Skip to content
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

MongoDB Atlas receiver configure granularity of metrics per project #36411

Open
williamlord-wise opened this issue Nov 18, 2024 · 1 comment
Open
Labels
enhancement New feature or request needs triage New item requiring triage receiver/mongodbatlas

Comments

@williamlord-wise
Copy link

Component(s)

receiver/mongodbatlas

Is your feature request related to a problem? Please describe.

Currently granularity is configured globally https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/mongodbatlasreceiver/config.go#L29

Supported granularity is different depending on instance type. The standard granularity is PT1M, but if any cluster within a project is M40 or greater, premium monitoring for the entire project is enabled, which allows PT10S.
https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/#premium-monitoring-granularity

It's not possible to configure the receiver with PT10S with a mix of both projects, as MongoDB Atlas API returns an error, made worse by the nature of the error which contains no details.

HTTP 500 Internal Server Error (Error code: "UNEXPECTED_ERROR") Detail: Unexpected error. Reason: Internal Server Error. Params: []

The feature would be to allow different granularity for projects. It would probably be too opinionated to default to the lowest granularity depending on instance type, configuration at the project level would be ideal for flexibility.

Describe the solution you'd like

A global granularity as is, and also a project granularity (ie. override the default), for projects that have premium monitoring these can then be specified to be PT10S.

Describe alternatives you've considered

Running two exporters, one for standard and one for premium, or running multiple exporters, one per project.

Additional context

No response

@williamlord-wise williamlord-wise added enhancement New feature or request needs triage New item requiring triage labels Nov 18, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage New item requiring triage receiver/mongodbatlas
Projects
None yet
Development

No branches or pull requests

1 participant