MongoByte
Welcome to the new MongoDB Feedback Portal!
{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.
Welcome to the new MongoDB Feedback Portal!
{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.
|
What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. |
We encountered the problem of granular Mongo Atlas or Сompass access control to projects. The existing roles are not enough. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
We want to grant users permissions only for the Cluster -> Query Insights and Cluster -> Real Time Performance Panel, so that users can block query shapes and exec |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
This functionality is important for managing queries and responding quickly to incidents. |
What steps, if any, are you taking today to manage this problem? |
We need to give our on-call engineers the ability to kill problematic queries and block query shapes during incidents. Atlas UI provides excellent tooling for this in Query Insights and Real-Time performance panel.
Currently, granting access to these features requires assigning overly broad permissions that also allow cluster management and direct database access — which violates our security policies.
We need a more granular role that permits only query management operations (kill op, block query shape) without broader cluster or data access.
this would significantly reduce our MTTR during query-related incidents by enabling on-call engineers to act immediately, rather than escalating to a smaller group with elevated permissions.