-
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/mongodbatlasreceiver] #31181
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
We generally strive to determine the least permissions necessary to pull the data. I don't recall specifically how these permissions were determined but perhaps @schmikei does. In any case, feel free to propose lesser permissions and we can validate whether they work. |
These permissions are only required for access logs. This is a limitation based off the MongoDB Atlas functionality to request these database access logs. https://www.mongodb.com/docs/atlas/access-tracking/#required-access |
Thanks @schmikei. I'm closing this since there doesn't appear to be any action to take. Please let us know if there is anything further @nunodomingues-td. |
Hello @djaglowski @schmikei |
Component(s)
receiver/mongodbatlas
Describe the issue you're reporting
Greetings everyone,
I have an inquiry regarding Logs permissions, specifically related to the receiver documentation, which states:
Are these permissions indeed essential? Is this limitation imposed solely by MongoDB Cloud, or is it a constraint inherent to the receiver?
Thanks in advance
The text was updated successfully, but these errors were encountered: