Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
173 results found
-
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 -
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.
17 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 -
Monitoring for WiredTiger data handles
Add process measurements for monitoring WiredTiger data handles.
From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :
While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.
but now there is no way to get this information except
db.serverStatus()
5 votes -
feature that allows a user to copy date/time from a specific point in Atlas metrics graphs into the computer buffer (to paste elsewhere)
it will be very helpful for Atlas customer and Atlas support if there was aa feature to clock on any point on the monitoring graphs, and copy the current time into the computer buffer - in order to paste the specific date/time information into a case
currently, if we click on a point we can see the time/date at the bottom of the chart, however we cannot copy it because as soon as we move the mouse, the time/date it is hidden from view
1 vote -
killAllSessionsByPattern and kill sessions
Please add killAllSessionsByPattern and kill sessions feature in Atlas UI
2 votes -
Make AWS EBS Burst Balance metrics available in Atlas UI
Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.
You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.13 votes -
Optimal way to fetch all paused and resumed cluster details in an Organization
Need to find out a way to fetch the entire cluster status (paused/resumed) for all projects in an organization in a single command/api.
This is required to keep track of the paused cluster remaining days and thus save a lot of unnecessary cost.
1 vote -
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 hour range of time is displayed, the time every two hours will be labeled.
However, if more than 1 day is displayed, the x-axis labels are less useful. The particular time once/day is displayed, but the day is not included. For example, when I display a week of data, 07:00 is highlighted on each particular day,…
2 votes -
Splunk connector for Atlas
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.
35 votes -
Database Access History: sort and export
Would be nice to export the database access history and/or sort by a column.
3 votes -
New view with connection statistics
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.
28 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.1 vote -
Webhook
Hi MongoDB Atlas Team,
Some of enterprise customers are left out with improper monitoring via Webhook to ServiceNow (an ITSM tool). Can you please improve on it so right set of fields can be included like "Priority", "Service", "Assignment Group" etc. other details which can be filled up via dropdown or entered manually so alerts to generate incidents via ServiceNow.
Regards,
Varun
Toyota Europe Database Team8 votes
- Don't see your idea?