-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/mongodbatlas] Add additional collected metrics #36525
Labels
Comments
StefanKurek
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Nov 25, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Seems like a good addition! Do you have specific API docs you can link on how you're going to source these metrics/if they require extended permissions? |
@schmikei We actually are already retrieving all of the data for these metrics already. No additional API calls would be necessary. |
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this issue
Dec 17, 2024
…telemetry#36694) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds additional disk and process metrics to flesh out available monitoring metrics from the API. No new API calls were needed as we were already getting this data already. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36525 <!--Describe what testing was performed and which tests were added.--> #### Testing New tests generated and ran. <!--Describe the documentation added.--> #### Documentation New documentation generated. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: schmikei <keith.schmitty@gmail.com>
mterhar
pushed a commit
to mterhar/opentelemetry-collector-contrib
that referenced
this issue
Dec 19, 2024
…telemetry#36694) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds additional disk and process metrics to flesh out available monitoring metrics from the API. No new API calls were needed as we were already getting this data already. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36525 <!--Describe what testing was performed and which tests were added.--> #### Testing New tests generated and ran. <!--Describe the documentation added.--> #### Documentation New documentation generated. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: schmikei <keith.schmitty@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
Describe the solution you'd like
mongodbatlas.process.cache.ratio
to be placed under a Process resource.mongodbatlas.disk.partition.throughput
mongodbatlas.disk.partition.queue.depth
to be placed under a Process/Disk resource.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: