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
-
Profiler chart scale
In the profiler page, the charts scale do not make sense.
The maximum values in the Y axis are very high which make the investigation very difficult if the actual values are smaller.
I suggest that Y axis values would be dynamic to each the research.1 vote -
Allow custom date range to be submitted in Query Profiler
Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.
It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.
16 votes -
Data Transfer Limit
since as documented there are limitation on network traffic in M0/M2/M5 instances, it is mandatory to have a metrics/alerts (also for free ones) to monitor this value in a 7d sliding window
10 votes -
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-0
Now 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-0
This 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 -
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 -
separate resources for monitoring function agent and database
To change the resources monitoring function agents which is currently using Shared resources, we prefer it to be on a separate host to have workload isolation
1 vote -
Add Elastic integration to Atlas
Add support to send cluster metrics to Elastic. Elastic has recently been putting a lot of work into their APM and logging solution, this is now a viable alternative to NewRelic and Datadog and is gaining traction. It would be great if Atlas supported sending metrics to Elastic. Please see below for references
https://www.elastic.co/apm
https://www.elastic.co/siemThe use case for this is the same as NewRelic or Datadog. I wish to monitor my Atlas clusters from inside Elastic, create dashboards and set up alerting
22 votes -
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 -
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 -
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 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.
16 votes -
Monitoring Integration with Azure Event Grid
Monitoring Integration with Azure Event Grid.
2 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.
11 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.5 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…
15 votes
- Don't see your idea?