Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
169 results found
-
Display replica set members' Availability Zone details
The AZ details (ideally including the AZ ID) for each replica set member would be helpful to display in the Atlas UI, mainly to easily verify nodes are distributed across AZs.
45 votesThank you all for your feedback!
We hear you loud and clear and are working on exposing these details in the next quarter.
-
typical query on collection report
From the collections tab, show an aggregation of typical queries (for that collection) to help discover index opportunities
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 -
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 issues due to resource intensive queries submitted through the BI connector.
Currently it is only possible to guess that an issue could be related to the BI Connector by viewing system resource use.
2 votes -
real time view for just one node
Given that I address certain kinds of queries to certain tagged nodes,
As a developer,
I would like to filter the "real time view" tab to show only activity for my tags
So that I can monitor how my application impacts its node1 vote -
audit log event when new project is created in an organization
add an audit log even when any user within the organization creates a new project. Currently you can see when a collection is created, but nothing for new projects. This is helpful for auditing and accountability purposes.
1 vote -
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 reuse and can't know its trend.2 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 -
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.
9 votes -
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)?
2 votes -
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.
2 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 -
Email notifications
We have configured several alerts and are having them emailed to us. The subject line of the email alert is something like "[External]Alert - <CLUSTER NAME> - 2021-04-08T12:26Z". We would like the subject line to show what exactly is the alert for - for example - if the alert is for "System Memory: Available has gone below 3.2 GB", we would like the subject to include this information. All the email alerts have the same subject line except for the change in time. Please consider this request. Thank you.
1 vote -
1 vote
-
Display the Atlas-generated replica-set name in the cluster Dashboard
This is an easy one, and it'll help a lot.
Inconvenience:
In the past, every time I created a cluster, the name of the replica-set was in line with the name of the cluster:
e.g.:
Cluster Name:asteroids-tracking
Replicaset Name:asteroids-tracking-shard-0Now when I create a cluster, the name of the replica-set is a random set of characters prefixed by "atlas-"
e.g.:
Cluster Name:asteroids-tracking
Replicaset Name:atlas-[randomChars]-shard-0This makes it unnecessarily difficult to find (in the Atlas Organization) the cluster referred to when I receive text message alerts. Mainly when you are in charge of so many clusters.
Additionally,…3 votes -
2 votes
-
Monitoring Integration with Azure Event Grid
Monitoring Integration with Azure Event Grid.
2 votes -
Database Access History: sort and export
Would be nice to export the database access history and/or sort by a column.
3 votes -
Metrics Collection
Any way could analyze and store all the queries we have made
Fields would be: execution time, IO, cpu usage, etc...
This collection would store only 1 or 2 months of data.1 vote
- Don't see your idea?