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

Atlas Monitoring, Alerts & Observability

Showing 287

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

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

killAllSessionsByPattern and kill sessions

Please add killAllSessionsByPattern and kill sessions feature in Atlas UI
Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

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...
Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 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
Guest over 4 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...
Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 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...
Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Duplication detection

One of our custmoers would like to see duplication detection as their project is spread out over various projects. Value: It is important as different regions create sometimes duplicates and duplicates can be avoided in advance.
Guest about 2 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 over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Metrics: Fix Y axis of "max CPU %" charts to 100%

In the various CPU % usage charts in the shard metrics, it looks like the upper limit of the Y axis isn't fixed, and it changes based on what the maximum value in the range of time being displayed is. For both normalized and regular CPU% values, t...
Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted