Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
179 results found
-
Zabbix
We should have Zabbix integration to monitor the performance of MongoDB Atlas.
Zabbix is OpenSource popular monitoring tool available and many of enterprise organizations use this tool.
Please add Zabbix in Integrate with Third-Party Monitoring Services.
6 votes -
Send alert on mongodb database users changes and permission changes
This will be a important tool to get alerted if any databases get exposed or hacked.
3 votes -
Send Alert when IP access list changes
Customer is requesting that an alert be sent out if project IP access list gets changed
22 votes -
Trigger execution details
It would be very useful to have some details provided in Atlas to trace the execution of the trigger, like the _id and operation type at a minimum. When a trigger executes the only information we see in Atlas is [
"Sent to AWS EventBridge"
].6 votes -
CPU Steal % on Azure
The CPU Steal % metric and alert seems to be currently implemented only for AWS. Please implement it also on Azure, as there is no easy way currently to get alerted if the underlying burstable VM (e.g. for M20) runs out of credits ...
5 votes -
Please remove the text-transform uppercase style on the graph axes.
I yelled out "WTF!" in the office when I saw that a steep peak in the graph indicated a query that took 8MS. Turns out it meant to say 8ms.
The M means Mega (one million). We, I assume, are all very familiar with it, and therefore I assume that I'm not the only one who automatically reads it as one million.
Note that I did not confuse the s and S. That is because the s and the S are much less visually distinct. Still it's technically incorrect too.
1 vote -
Allow threshold on "System Memory: Available" alert condition to be a percentage
In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.
10 votes -
Ability to get collection stats via the API
e.g. list collections, collection size, collection indexes, etc.
3 votes -
Increase monitoring metrics resolution retention time on views of 1min & 5mins
The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.
After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.
I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.
22 votes -
Support db.setLogLevel() in Atlas
I'm testing wire compression in the drivers, the results of which is only set to verbose log levels (see: https://github.com/mongodb/specifications/blob/master/source/compression/OP_COMPRESSED.rst).
I'm not sure how to validate wire compression is making its way to Atlas w/out this capability. The setting would revert when the server is restarted, so it shouldn't have too big an impact on our log file sizes.
1 vote -
Automatic information when shared cluster is throttled
When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.
Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.
18 votes -
Allow the image export using Atlas Admin API
For the report purpose, we need to get the exported images of Status/Hardware/DBStast.
With personal authentication, I can get these images via URL:
https://cloud.mongodb.com/export/v2/charts/{status/hardware/dbstast}/{clusterID}/{hostID}/{format}/{title}?since={since}&until={until}&hostDbStatsName={DBName}However, I cannot get it programmatically with API Key authentication.
Let's allow the image export using Atlas Admin API.
Thanks!1 vote -
Show max IOPS line on IOPS graphs
When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.
19 votes -
Disk queue length metric
Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).
Would it be possible to add this metric to Atlas monitoring?
11 votes -
track collection size
I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?
5 votes -
Keep context of Metrics dashboard
on MongoAtlas metrics dashboard, I can organize graphically different metrics as I want to display first "insert" metric for example, then "cpu" metric, etc ...
If I change this actual order, then I go to another screen (for example "network access") and finally I come back to this metric dashboard, my new metrics added (insert, cpu, ...) in first position are not in wanted first position (at the top of metrics list), but at the end of this metrics list.It would be great to keep metrics context (displayed metrics and ordering) on Metrics dashboard.
8 votes -
External database connectivity monitoring
We had an incident where the PRIMARY node was considered healthy internally and could communicate with other nodes but lost connectivity with other external services. In these type of cases it would be great to have external connectivity monitoring that can detect whether the PRIMARY is accessible from outside of the cluster.
1 vote -
Show date in UI DB Stats axes
Show date in UI DB Stats axes
Currently the x-axis of DB Stats charts do not show dates, making it difficult to interpret the range of time displayed in the chart.
For example, you can see in the date menu shown in the attached image that the chart range is over 4 days, but this is not apparent in the x-axis of each chart -- the x-axis only shows one reference time of 07:00.
It would be more helpful if the axis showed a reference date in addition to the time, and ideally a couple dates so that it is…
4 votes -
Log Redaction for Atlas
It would be good to see Log Redaction work in Atlas as well, similar to On Prem
https://docs.mongodb.com/manual/administration/monitoring/#log-redaction4 votes -
Add Process CPU metrics for `mongos`
Currently the
Process CPU
andNormalized Process CPU
metrics for all clusters appear to only show the CPU formongod
. For sharded clusters, please add a metric to trackmongos
(and possiblymongot
, for those using it) usage.2 votes
- Don't see your idea?