Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
181 results found
-
Would love to have a little bit more info in the webhook to know what caused the election, or that there was an upgrade (vs a server failure
Would love to have a little bit more info in the webhook to know what caused the election, or that there was an upgrade (vs a server failure) in the db!
MongoDB AtlasAPP 12:10 PM
Project: myProjectOrganization: myProject (Organization)
INFORMATIONAL
Replica set elected a new primary
my-cluser-shard-0
Created: 2020/01/03 11:10 PST
Replica Set: my-cluser-shard-0
Current Member State
DOWN: 1 member
SECONDARY: 1 memberPRIMARY: 1 member
love the service team, thanks a ton!2 votes -
Profiler Filters
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
- readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
- Also, when Operation = command, it could actually be many things.…1 vote -
Add application connection details
It would be really helpful to be able to see application connection details on Atlas monitoring. The "real time" only shows active collections. I want to see which applications are connecting, active, and what queries are they running etc. At this moment, we don't have that on Atlas web console. Please consider this feature to be added in the coming future.
1 vote -
Show Mongos Connection Number in Overview.
Currently, the connection number shown in Overview is shard connection, it is the connection from Mongos to Mongod, which should usually be lower than the Mongos connection.
The connection limit for MongoDB is referring to Mongos connection which should be shown in overview or otherwise very misleading when we received connection % alert.1 vote -
index stat
Merge index stats from all replicas in index page UI, and enable the reset stats in UI.
Preferably merge all stats from all shards and show it is coming from a secondary replica or a primary replica. Current index stats in UI only show primary stats and it is not useful.1 vote -
Notification "Failed maintenance"
It would be helpful to have a "Failed maintenance" notification. While we cannot resolve the issue ourselves in such cases and need to open an Atlas support ticket, it is still important for us to receive a notification so that we are informed about the problem and can respond accordingly.
1 vote -
Query profiler drilldown by number of write conflicts
One sort of issue that can lead to elevated CPU utilization but is otherwise hard to identify is queries with high numbers of write conflicts. Having some way to drill down to queries that exhibit these symptoms would be quite convenient.
1 vote -
Forward MongoDB Atlas logs to Securonix
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Securonix.
1 vote -
Properly Formatted Prometheus Integration (mongodb_ metrics)
The (mongodb*) metrics collected by the integration lack the metric type and the description is extremely vague (mongodbcatalogStats_views has "catalogStats." as description). It would be easier to setup dashboards and queries if the type (e.g., gauge, counter) was properly set up and the metric provided a proper description.
1 vote -
View cluster/storage scalable (yes/no) in "All cluster" dashboard
Right now in the "all cluster" view, one cannot see, if the clusters are enabled for auto scaling. my idea is to add this also to avoid last minute performance alerts for non scaling enabled clusters
1 vote -
Collection query audit logs
It would be nice to be able to see what queries were run on which collection over the last x days.
1 vote -
MongoDB Atlas historical stats by collection
It would be helpful to have historical metrics for storage by collection. Storage space used, indexspace used, number of indexes.
Thanks1 vote -
Improve Metric Correlation
Would be nice to better correlate metrics, server events, and individual operations.
For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them in the last 24h.
1 vote -
Throttle instances within a shared tier
Right now, if a cluster is in a shared tier, other "noisy neighbor" tenants can destroy performance by overusing the resources, forcing a restart, causing unstable behevior etc.
Throttle noisy neighbors so that others don't suffer!
1 vote -
Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs
We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements.
E.g. User is investigating current lags in the data Layer. User has to select all the metrics that would help them get the data they are looking.
We can help the customer bit more by provide buckets like.
Options ( select one )
1. Investigate Lags
2. Investigate IOPS
3. Investigate Replication
4. Investigate Search Index
... and etc..This will pre-select certain metrics from list of Mongodb & Hardware metrics which will give them all…
1 vote -
Export only selected Atlas metrics
This is a request from a customer named: UPAX partnered with Grupo Salinas.
Inside the cluster metrics, where the Status is displayed, we are able to find the Export option (PDF, PNG) and they would like to export for only specific metrics (only the toggle charts) not the whole of them for reporting purposes with other teams and management.1 vote -
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.
1 vote -
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, there's a natural maximum to the value, I think: 100% for the normalized CPU%, and ncores*100% for the non-normalized CPU%.
With a changeable Y limit, it's hard to tell at a glance whether the value is actually really high or not. Oh, the blue line is hovering up near the top of the…
1 vote -
Display all function log messages
Currently we only can see under "App Services > Manage > Logs" section the output of a few log messages for each function execution, but if the function contains a large amount of logs (more than 100 for example) the interface only shows the last log entries, making difficult to debug and check for errors.
There is should be way to see all logs output of a function execution.
Forum reference: https://www.mongodb.com/community/forums/t/atlas-functions-seem-to-not-display-all-of-the-logs-when-running-in-web-ui/194108/6
1 vote -
Display "N/A" instead of "0" for doc count in timeseries collection in Compass
In Compass 1.36.4, when I look at a database that has a time-series collection in it, in its list of collections, it displays the collection as having "Documents: 0" and "Avg. document size: 0", even when there are some documents in it.
I think that's misleading. As I understand it, time-series collections do not support the estimated document count functionality that is used to populate these fields in the Compass GUI. That being the case, it might be better to display "n/a" or a blank in those fields, instead of a 0 which is not the correct value. A user…
1 vote
- Don't see your idea?