All feedback

Showing 3959 of 3959

Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.

Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it. But it would be nice to be able to specify a def...

Guest over 4 years ago in Atlas 0 Submitted

3 VOTE

Sydney nodes for atlas charts

It would be great if we could get some nodes to serve APAC for charts to bring down the latency a bit, rather than having to go to us-east-1 AWS region. I imagine this is planned as Stitch already has nodes in Sydney but I thought I would make a ...

Guest over 6 years ago in Charts 0 Future Consideration

2 VOTE

Is it possible to export the collection without rearranging the columns in alphabetical order, I prefer them they way they are as-is. Thank

No description provided

Guest over 4 years ago in Compass 0 Submitted

1 VOTE

Atlas UI Custom RBAC

Our organization leverages Okta for SAML/SSO authentication, and have terraformed our role mappings to the MongoDB Atlas provided Org and Project roles. There is currently a feature to create custom DB roles, however, custom RBAC for the Atlas UI ...

Guest about 2 years ago in Compass 0 Submitted

2 VOTE

Add Process CPU metrics for `mongos`

Currently the `Process CPU` and `Normalized Process CPU` metrics for all clusters appear to only show the CPU for `mongod`. For sharded clusters, please add a metric to track `mongos` (and possibly `mongot`, for those using it) usage.

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

1 VOTE

add index on oplog collection which will avoid full collection scan where change stream enabled , as of now full scan causing high cpu

add an index on oplog collection for change stream to avoid full collection

Guest about 2 years ago in Database 0 Submitted

2 VOTE

Respect custom roles/Specific Privileges

Currently Compass does not respect collection privileges properly. If you limit access to a particular collection in a DBuser assigned role or specific privileges it shows you no collections. I have confirmed this with customer support as demons...

Guest over 4 years ago in Compass 1 Submitted

2 VOTE

Respect custom roles/Specific Privileges

Guest over 4 years ago in Compass 0 Submitted

1 VOTE

Triggers - resume via CLI

Currently the only way to resume a suspended Trigger is via the Admin API: https://realm.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/triggers/{triggerId}/resume It would be more convenient via the Atlas CLI

Guest about 2 years ago in Atlas Triggers and Functions 0 Submitted

2 VOTE

allow control of pagerduty urgency (currently high) so that alerts can be managed better

Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Please enter your email address

FILTER BY CATEGORY