-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics
-
Networking & Observability
-
Fully Compatible
-
Networking & Obs 2025-01-06, Networking & Obs 2025-01-20
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The metrics under serverStatus.network only account for the network traffic of ingress connections (see SERVER-6227). Extending the metrics to also include egress connections, those established by a mongo process, would help diagnostics and monitoring. This ticket requires the following:
- Defining new metrics (e.g., egress.physicalBytesOut and egress.physicalBytesIn) for egress traffic.
- Separating egress and ingress metrics in serverStatus.
- Creating a ticket to update the documentation for network metrics in serverStatus.
- has to be done before
-
SERVER-99389 Move numSlowDNSOperations to egress section of network metric
-
- Backlog
-
- is depended on by
-
COMPASS-8836 Investigate changes in SERVER-51832: Provide network metrics for egress connections
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-6227 Definition of serverStatus.network.bytesIn and bytesOut are not consistent with regards to replication traffic
-
- Closed
-