You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are a number of metrics available that are useful (and that may already be collected from the API as far as I can tell), but not currently being made into metrics. Adding these metrics would help to have parity with the monitoring graphs that MongoDB Atlas has to offer natively.
The list is:
mongodbatlas.process.cache.ratio
mongodbatlas.disk.partition.throughput
mongodbatlas.disk.partition.queue.depth
Metrics for the count of databases & the counts that mongodbatlas.db.counts currently provides but at the Cluster resource level (vs the current Processor/Database level) could also be useful, but I'm not sure how well these would fit within the current pattern for this receiver.
Describe the solution you'd like
Add new metrics: mongodbatlas.process.cache.ratio to be placed under a Processor resource.
mongodbatlas.disk.partition.throughput mongodbatlas.disk.partition.queue.depth to be placed under a Processor/Disk resource.
If I can think of an unobtrusive way, add an aggregate way to show mongodbatlas.db.counts for the entire Cluster as well as a mongodbatlas.db.count type metric which would show the count of databases for the Cluster.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
receiver/mongodbatlas
Is your feature request related to a problem? Please describe.
There are a number of metrics available that are useful (and that may already be collected from the API as far as I can tell), but not currently being made into metrics. Adding these metrics would help to have parity with the monitoring graphs that MongoDB Atlas has to offer natively.
The list is:
mongodbatlas.process.cache.ratio
mongodbatlas.disk.partition.throughput
mongodbatlas.disk.partition.queue.depth
Metrics for the count of databases & the counts that
mongodbatlas.db.counts
currently provides but at the Cluster resource level (vs the current Processor/Database level) could also be useful, but I'm not sure how well these would fit within the current pattern for this receiver.Describe the solution you'd like
mongodbatlas.process.cache.ratio
to be placed under a Processor resource.mongodbatlas.disk.partition.throughput
mongodbatlas.disk.partition.queue.depth
to be placed under a Processor/Disk resource.mongodbatlas.db.counts
for the entire Cluster as well as amongodbatlas.db.count
type metric which would show the count of databases for the Cluster.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: