Feedback

Should be possible to configure profiling output destination

When enabling database profiling the output is sent to both the system.profile collection and system logs. Logging to a capped collection is fine but spamming the logs on disk is not good. We have a need to be able to react to changing query patt...

Guest over 2 years ago in Performance & Optimization 0 Submitted

9 VOTE

Enable Atlas Maintenance Notification without specifying a maintence window

There should be an option to enable Alert notification for Atlas maintenence without specifying an Alert Window. Just because a specific window is not required, MongoDB Atlas should allow an option to receive notification that one occurred. This w...

Brad Meyers over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

16 VOTE

Higher IOPS for small disk sizes (MongoDB Atlas on Azure)

AWS and GCP start with 2300-3000 IOPS for M10+ instance from the smallest disk size (8Gb), whereas on Azure we get 120 IOPS with 8Gb, 240 with 64Gb, 500 IOPS with 128Gb ... nowhere near to what AWS/GCP offer (120 - 500 IOPS for a database server i...

Guest over 4 years ago in Database 2 Submitted

9 VOTE

Add document count to Datadog metrics

We'd like to monitor the number of documents in a collection via DataDog. For On-Premise MongoDB the stats are already reported via mongodb.collection.count, mongodb.collection.size and mongodb.collection.avgobjsize. If the same metrics could be...

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

13 VOTE

Release notes with urgency and risk

Provide MongoDB customers/users with an understandable release notes, especially for bugfixes. **What are the risks this bugfix release covers, what is its urgency**. Right now, release notes are made of MongoDB Jira tickets, which are very detai...

Guest almost 4 years ago in Database 0 Submitted

15 VOTE

Add an alert or notification option for every "pause" or "resume" cluster action

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

18 VOTE

Alerts Messaging Customization

At the moment, it appears one cannot customize the messaging or subject line of the alerts. This makes it difficult to categorize the alerts. For instance, we would like to categorize alerts into different severity levels, such that severity level...

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

8 VOTE

Ability to "Mass Kill" slow running queries

Currently, Atlas has a "Kill Op" option which is useful to kill single long-running queries. When upgrading to MongoDB 7.0, we were faced with a situation where the Slot-Based Query Engine (SBE) was causing 1000s of queries to execute slowly, we ...

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

1 VOTE

MongoDB missing support for GeoJSON-compliant indexing+intersection queries

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 are building a geospatial application that uses GeoJSON natively. We need to query MongoDB for a list of GeoJSON object...

Mitchell Horning 4 months ago in Querying & Aggregations 0 Future Consideration

8 VOTE

Lock on session start level with provided keys

Scenario: Parallel DB updates with transactions on multiple collections that use same documents. Example: Calculate some common stuff to embed it in extra collections to avoid lookups. Problem: Lock and timeout on documents uses up valuable time ...

Guest over 2 years ago in Storage & Transactions 0 Submitted

Please enter your email address

FILTER BY CATEGORY