-
Notifications
You must be signed in to change notification settings - Fork 3k
Description
Component(s)
receiver/mongodbatlas
Is your feature request related to a problem? Please describe.
Hi Team,
We have multiple ATLAS organizations in our setup and projects are created and deleted frequently. This makes the maintenance of the atlas receiver configuration difficult as frequent changes are needed to our otel configuration. Due to safety reasons, we have manual review and approval for the pull requests (changes to config.yaml / values.yaml need to be pushed for each project creation/deletion).
Describe the solution you'd like
We understand this behavior is designed for security reasons. However, we would like to have an option where by we can also have option to take all projects ( may be a new parameter? )
Our request is to have an option where by default the receiver takes all projects in an organization similar to the behaviour with clusters. i.e provide an option where if we do not specify include/exclude projects, the receiver should retrive all projects ( just as the same way it works for clusters ).
Describe alternatives you've considered
We have automated the process of updating the project list for each organization for each new project addition or deletion, however, since the merge part is still manual ( due to security reasons ), it makes the continuity of the observability for affected Atlas organizations.
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1
or me too
, to help us triage it. Learn more here.