It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.

Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).

screenshot: https://p-37FYgJ.b1.n0.cdn.getcloudapp.com/items/L1upe7Wv/Image%202020-06-25%20at%204.28.22%20PM.png?v=ec3b0551ea4035a207a90ab83817bba6

12-hour time is not widely used around the world, and it is cumbersome to use in the date pickers especially give that other parts of the UI use 24-hour time.

Can we update these date pickers to use 24-hour time instead?

Our main concern is 'Host experienced a rollback' is not an alert option!

Ideally, anything that shows up in the activity feed should be available as an alert.

Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.

It would be valuable to have a per-cluster view showing an overview of connections into each cluster including:

• The number of connections per hours (opened, closed == churn)


• Which IPs connections are coming from and how many from each over time


• What drivers are being used for these connections and from which IPs


• Which user is opening the connections

This information can be very useful in understanding which applications/microservices are opening up the most connections, and helping to find old drivers etc.

We need a way to easily ingest logs into Splunk. It needs to be all logs - node and web portal activity. Ideally a Splunk connector would be provided but a stop-gap measure would be the ability to configure Atlas to write all logs to an Azure storage account.

Lack of native log ingestion ability may be an Atlas deal killer for us.

Add alerts for when Triggers are suspended or exceed a threshold.

The alert payload only contains status field with 'open' or 'closed' value. No severity definition option is available.

When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.

Currently there is only a community supported Prometheus integration (exporter) available which polls db.serverStatus() and doesn't include as much metrics as the Atlas UI/API provides. A similar integration as with New Relic and Datadog would help many customers that are using Prometheus and Grafana for monitoring.

It would be useful to provide the profiler an "allowlist" and "denylist" of users to watch queries from. Essentially, it is only useful to receive alerts and profiler reports for queries made by actual applications. It is not useful to have alerts show up for one-off queries made by a DB admin using a DB explorer.

We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...

Even better, make a collection with it.

Please include eviction metrics as well in monitored metrics in atlas so that it will provide an overview how many evictions are happening in particular time and there by decide correct memory for the instance.

The NewRelic integration in MongoDB is using the default NewRelic API that is in non-EU region. There is a separate API endpoint for EU region, that is described at https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#.

This is causing 'newRelicLicenseKey' failed to authenticate error for the MongoDB Atlas cluster setup in EU region.

With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.

The Atlas activity feed is currently searchable by Type of event. It should have an option to search by cluster name to quickly narrow down any particular activities relating to a particular cluster

This is a request to add some additional metrics to those that are currently sent from Atlas to New Relic when the integration is enabled.

The specific metrics of interest here are:
- Disk Space (%) Used (or Free)
- DB Storage
- Query Targeting

Having pointed out the above metrics specifically, I would also say: the closer that the metrics sent to New Relic via the Atlas integration can resemble those available in the Atlas cluster Metrics page, the better.

Hi,

Can you please create an alert for WiredTiger metrics, such as used cache?

We had several cluster instances going over the 5% of used cached (dirty data) and would like to be notified when it happens.

Regards,
Sergei

This is needed in order to determine whether