Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
161 results found
-
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 -
2 votes
-
Allow log level to be configured per cluster/node
Atlas clusters don't support the setParameter command and, as a result, users aren't able to configure log levels. I understand the reasoning behind not exposing permissions to run setParameter to DB users so, in lieu of that, it would really helpful if Atlas users were able to configure log levels through the Atlas UI, preferably at the Node or Cluster level.
Thanks!
10 votes -
Monitoring Integration with Azure Event Grid
Monitoring Integration with Azure Event Grid.
2 votes -
Monitoring Integration with Splunk
Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.
13 votes -
Graph connections per user (or per database)
Show a graph of connections per user.
It would be very useful to see how many connections each user has (or also, each db) over time.
It would allow us to see more clearly and faster which service uses how many connections.
10 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 -
Show driver/application/user metadata in Query Profiler query summaries
It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.
After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.
This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).
This information…
14 votes -
3rd Party Hooks
Within Atlas today, we have a number of channel options to send alerts (Ex. OpsGenie, Slack, VictorOps).
I would like to see a hook integration provided by Atlas so any tool can recieve alerts from their cluster. Ex. I can recieve my cluster alert in Microsoft Teams.
3rd party hooks can increase the stickiness of Atlas and improve freedoms for teams and their existing toolsets.
3 votes -
Atlas Cluster Labels in UI
With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.
18 votes -
Metrics
We would like the possibility to freeze the row S S P (freeze the top row) when we scroll down to the different charts.
2 votes -
Custom replica set tags
Currently Atlas comes with pre-defined Replica set tags such as Provider, Node Types, Region.. But as of now no options for user-defined tags.
Please provide options for custom/user-defined replica set tags.4 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
-
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 -
Alerts based on Activity Feed - Rollback
Our main concern is 'Host experienced a rollback' is not an alert option!
Ideally, anything that shows up in the activity feed should be available as an alert.
11 votes -
Elections bar colors in Metrics should be more vivid
The atlas metrics show node election statuses in colors - red/orange and brown. When there are multiple re-elections in a short period of time, these all merge together making it hard to decipher the order of occurrence - especially the near overlap of orange and brown Having vivid/contrasting colors should make debugging easier.
It would be helpful if some aspect about the x-axis would tell you what status the node was in at a given time. For example: the x-axis is also that color from time X to time Y, and then the node was demoted/down and the axis turns…
22 votes -
Show total disk size and index size used for each cluster prominently so we can upgrade if we need to
Right now, I do this manually. Would be good to see the totals prominently, along with a recommended upgrade/ not next to it, and single click to select the next size.
1 vote -
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 -
Make RSS feed entries more consistent
We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.
4 votes
- Don't see your idea?