Skip to Main Content

MongoByte MongoDB Logo

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.

ADD NEW FEEDBACK

Feedback

Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale

Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale Currently, when a mouse is not hovering over a Metrics plot, the plot will show particular hours as labels for the x-axis. For example, if an 8 hou...
Marie Atterbury almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

logs

When filtering logs I should be able to enter a date/time in the near future for the To date in order to produce a shareable URL in the address bar that will include log lines in the range from some specified date in the past until "now" without h...
Guest almost 5 years ago in Atlas Triggers and Functions 0 Submitted

Allow Monitoring IOPS Credit Balance for AWS gp2 volumes

Allow users to monitor their IOPS balance on burstable gp2 storage volumes. See I/O Credits and burst performance in https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html
Kai Orend almost 5 years ago in Atlas Monitoring, Alerts & Observability 1 Will Not Implement

The Atlas Disk IOPs Read/Write alerts for data/index/journal partitions should be combined & not reference partitions.

The current Atlas Disk IOPs Read/Write alerts are for data/index/journal partitions. However, Atlas does not use seperate partitions for data/index/journal so it can be misleading to rely on the alert message. The Atlas Disk IOPs Read/Write alert...
Charles Merrill almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Retry function

We use Realm functions to update related documents in our Mongo Atlas cluster. Sometimes, the DB connection (via `context.services.get("mongodb-atlas")`) fails. We should... be able to retry establishing a connection? (Or even easier, just configu...
Guest almost 5 years ago in Atlas Triggers and Functions 0 Submitted

Show BI Connector resource use Metrics

It would be helpful to be able to view the resources used by the BI connector in Metrics, similar to how you can view resources used by Atlas Search (Search Disk Space Used, Search Normalized Process CPU, etc). This could help with identifying iss...
Marie Atterbury almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Bytes available for reuse metric

This metric will show the available bytes for reuse. If it's too much and its graph is changed a little bit, we can decide to compact it for saving cost (from disk usage). Currently, we have to run dbstat command to see the available bytes for reu...
Guest almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

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 over 2 years ago in Atlas Triggers and Functions 0 Submitted

Ability to block sending of Alert Close Notification

We have set up alerts and have noticed that when a condition is back to normal, there is another alert generated acknowledging its closed. Is there a way we can manage this (like disable or block it for some alerts)?
Guest almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

High resolution monitoring and alerting for WT dirty cache ratio, eviction workloads and checkpoints.

Implement better monitoring and alerting for WT dirty cache ratio. This should include sub-minute resolution and support an understanding of eviction workload as well as performance impact of checkpoints under heavy write workloads.
Guest almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted