MongoDB topology label ClusterID is not unique
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Attachments
1
- 19 Aug 2022, 08:17 AM
Smart Checklist
Activity
Show:
Puneet Kala August 19, 2022 at 8:28 AM
Identification of cl_id was fine, these services belonged to the same cluster were just added for monitoring in a different way
Not a Bug
Details
Details
Assignee
Unassigned
UnassignedReporter
Denys Kondratenko
Denys Kondratenko(Deactivated)Priority
MediumComponents
Needs QA
Yes
Needs Doc
No
Affects versions
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created August 19, 2022 at 8:19 AM
Updated March 6, 2024 at 12:48 AM
Resolved August 19, 2022 at 8:28 AM
User impact:
Can't identify and filter different clusters in MongoDB metrics.
Steps to reproduce:
@Puneet Kala has a cluster setup that reproduces this issue.
Actual result:
All cl_id are the same.
Expected result:
unique cl_id
Workaround:
`cluster` custom label when adding the service.
Details: