-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Cluster name disabled for mongodbatlasreceiver metrics #31842
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @preshit1505, all of the resource attributes and metrics in
|
Hello @crobert-1 , I have not been able to make it work. How can i enable it in my collector config? Do we have any flag to enable? I only see labels like projects, organization, page_size, types in EVENTS |
The configuration I shared in my comment should enable the resource attribute to be ingested by the collector. Are you able to add the |
ohh so this block can be added directly in the collector config. This is my current config:
|
That's correct, sorry, I should have been more clear with that. You should be able to just add it to your config to enable it. Something like this:
|
wow awesome @crobert-1 i will try this and let you know here if that works. Thanks for your quick responses. Really appreciate that |
@crobert-1 omg it WORKED. Thank you so much for this help. |
Glad to hear it! Happy to help 👍 |
Component(s)
receiver/mongodbatlas
Is your feature request related to a problem? Please describe.
We are trying to create mongodb atlas grafana dashboard where we using the mongodbatlasreceiver in our OTEL collector to get the metrics. Since the mongodb_atlas.cluster.name in metadata.yaml has been disabled, which causes not able to filter the metrics data based on the cluster name
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/mongodbatlasreceiver/metadata.yaml#L34C2-L37
Describe the solution you'd like
solution for the above issue would be enabling the cluster name filter in the metrics
Describe alternatives you've considered
As of now, we dont really have an alternative to resolve this issue in our dashboards
Additional context
No response
The text was updated successfully, but these errors were encountered: