Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- otel-improvement
- otel-metrics-urgent

Assigned Teams:

Networking & Observability
Sprint:
N&O 2026-03-30, N&O 2026-04-13
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

For now, OTel metrics are duplicated into server status to maintain compatibility. We display the metrics in the format "network.connections_processed_connections" in server status, but the convention set by server status is to use the dot as a delimiter to created nested metric trees.

As an improvement to stay in line with current reporting, we can repurpose the logic in the MetricTree class to display otel metrics like this when dumping them to BSON.

This isn't a breaking change in either direction, but could be nice to stay with convention.

is depended on by

SERVER-123062 Adjust cursor serverStatus metrics on mongoD to use new OTEL API

Open

SERVER-123063 Adjust cursor serverStatus metrics on mongoS to use new OTEL API

Open

is duplicated by

SERVER-122611 Extend OTEL server API with alternative path for serverStatus

Closed

Assignee:: Cheahuychou Mao
Reporter:: Erin McNulty
Participants:: Cheahuychou Mao, Erin McNulty
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Feb 05 2026 09:14:08 PM UTC
Updated:: Mar 31 2026 10:02:57 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates