Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
175 results found
-
Add support for replication lag and replication headroom metrics in Datadog
The metrics replset.replicationheadroom and replset.replicationlag would be useful to have exposed to identify network limtiations and/or too small oplogs
2 votes -
Allow to set billing alerts per project
I have different projects where I expect and calculate with different costs. I would like to set billing alerts per project, for example if an internal evaluation projects execeeds a specific biling the threshold is probably lower then for a production project.
Similar to the currenty billing alerts, I would to set a billing alert, but either per project or with different thresholds for each project.
2 votes -
Option to group Profiler records by query pattern
The Profiler shows slow query statistics grouped by namespace, but it would also be helpful to view query records grouped by query pattern (perhaps similar to the "pattern" group option in mplotqueries: http://blog.rueckstiess.com/mtools/mplotqueries.html#group-by) and/or by specific fields used in the query.
This could be helpful, for example, for identifying particular query shapes that are executing slowly or suboptimally so that these can be investigated in more detail.
2 votes -
Add full screen mode for multi-graph Metrics and Status views
Unless I've missed a button somewhere, it would be nice if the "Metrics" tab for clusters and "Status" tab for shards had an option for expanding the entire tiled graph view into a full screen view. We have some TVs around our dev pod where we display these graphs and it would be great to see several graphs at once in full screen view.
2 votes -
Allow bulk changes to alerts - e.g. changing slack channel
Changes alerts is really painful. For one thing, pressing the Enter key doesn't close the dialog and nor does pressing Escape.
This makes it really painful to change something simple like the slack channel used for alerts.
2 votes -
Credits by period
Provide the ability to display and export credits by period (from date - to date) instead of selecting each single month, so that uers can easily display credit trends, etc. without downloading a lot of cvs and merge them togheter.
2 votes -
Add a Transaction Commits / Sec Metric Graph to Atlas
Add a graph in Atlas to display "transactions.totalCommitted" on a per second basis to the Atlas metrics UI. Customers that are using transactions are often more interested in the # of transaction commits per second than opcounters.
I have had to use mongostat on a number customer evaluations because this metric is not available.
2 votes -
Allow to resend alert to a PagerDuty service
Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.
The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.
Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.
2 votes -
Precautionary Change/Recommendations for Shard Drops
If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).
2 votes -
Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build
During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.
However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…
2 votes -
Identification and labelling of MongoDB connections
It'd be REALLY useful if there was an ability to provide a label (basically a string) when creating a new connection to MongoDB from an application, to say where the connection is coming from.
For example we use a bunch of microservices and each API sets up a new connection. It'd be very useful to be able to see how many connections each API has at any given point, as it'd allow us to determine if the microservice is misbehaving with the database etc.
2 votes -
Show node region on the metrics tab
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.
2 votes -
Disk Usage Breakdown
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.
2 votes -
Metrics "seconds" improvement
The uppercase "S" on the metrics which indicates seconds, can be slightly misleading as it can appear to be the number 5 when placed next to another number. This is especially misleading on the Replication Lag metric. It may be easer to read as a lowercase "s" or abbreviating with "sec".
2 votes -
Invoice: Ability to post items to a collection daily
You have daily line items on invoices. It would be great to be able to configure our billing to post to one of our collections. This would allow me to put charts on top of usage across all of our project and not just monthly
2 votes -
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 -
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
- Don't see your idea?