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
-
Stream profiler data to external services
Currently there doesn't seem to be a way to set up custom alerts and monitoring on specific metrics such as when the size of documents returned form a query exceeds a certain limit, even though that information is available through the Profiler when looking at query samples.
It would be very useful to be able to either configure these metrics to be sent to an external service like Loggly for better monitoring and alerts or allowing to create customized alerts/webhooks within Atlas that would be triggered based on a custom-specified condition.
1 vote -
Use 24-hour time format in Metrics date pickers
Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).
12-hour time is not widely used around the world, and it is cumbersome to use in the date pickers especially give that other parts of the UI use 24-hour time.
Can we update these date pickers to use 24-hour time instead?
5 votes -
Atlas activity feed
We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...
Even better, make a collection with it.
6 votes -
Profiler window should auto zoom to sampling period and show sampling period range
Atlas documentation states that the Query Profiler shows up to 10,000 queries within the past 24 hours: https://docs.atlas.mongodb.com/tutorial/profile-database/index.html#data-display-limitations
However, it is confusing to see that the Profiler cannot show more than a couple hours of data, likely because it is hitting the 10,000 entry limit.
The plot still shows a view showing 24 hours of time, but only the past couple hours have data plotted, misleadingly indicating that there are no slow queries before a couple hours ago – here's an example: https://p-37FYgJ.b1.n0.cdn.getcloudapp.com/items/JruWZDYK/Image%202020-03-25%20at%2010.49.32%20AM.png?v=7f79362e62c8d15a9f91f8ba4d5aecaf
Atlas should make the sampling time window clear in the Query Profiler graph so that we…
9 votes -
Ability to search for filter conditions in Atlas Alert builder
It would be helpful to be able to search for a trigger condition in the Alert builder when creating/editing an alert.
Currently, you need to scroll to find specific conditions, but the list is long so it can take some time to find the particular one needed.
4 votes -
Change Atlas Metric Timeline Annotations Color
Filing this on behalf of customers that are having a hard time telling orange and brown apart in Atlas metric timeline annotations (node become secondary, node becomes primary)
1 vote -
Show a graph of BANKED iops (AWS)
Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)
Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight…
11 votes -
The page fault metric is not available in the Datadog integration
The page fault metric is not available in the Datadog integration
3 votes -
metrics
There might already be a way to do this, but I cannot find it. Please provide a way to combine "all primary" metrics into a single chart.
I love your metrics, but I hate that when primary moves from one server to another I get "data gaps" in my graphs. So then it becomes exceedingly difficult to look at temporal variations... requiring splicing together multiple segments from 2 or 3 different graphs.
I have attached a picture of what I am talking about. You can see that primary moved over for a few days so I get a graph with…
9 votes -
Allow NewRelic integration to use EU APIs instead of default US APIs for clusters in EU region
The NewRelic integration in MongoDB is using the default NewRelic API that is in non-EU region. There is a separate API endpoint for EU region, that is described at https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#.
This is causing 'newRelicLicenseKey' failed to authenticate error for the MongoDB Atlas cluster setup in EU region.
5 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 -
Display chart annotations more conspicuously
To access chart annotations, users have to first hover over the metrics display, click on the info icon next to the title of a specific metric, and then read the annotations under the explanation of that metric. I didn't know they even existed until a support person happened to mention the vertical lines and I asked what they were. It would be more user-friendly to have the annotations (really, a legend for vertical lines) displayed separately in a more conspicuous location. Maybe in an info icon next to the annotation toggle? Another option would be for the vertical lines to…
1 vote -
Mongodb atlas logs - IP whitelist information
Hi Team,
We understand that network whitelist information (IPs added/removed) will be available only in portal under project activity feed. As our requirement is to access this information via API.Please let us know is there any feasibility of having these project level network whitelist information through API or in db logs in near future.
1 vote -
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 -
Add replica set name to cluster info main page
It would be nice to get quick access to the name of the replica set from the cluster overview page.
6 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 -
Allow to create Dashboard
Please provide feature to create a dashboard for metrics like CPU, memory consumption etc for a cluster or more than one cluster in single graphs like for cpu one graph, for memory one graph like that just like monitoring tools provide for example zabbix screens and dashboards, stackdriver dashboards, dynatrace dashboards.
This is to have a glance on our entire architecture instead of checking each and every cluster every time. This will be particularly useful during load tests or business peak period where we need to check more than one cluster performance.
4 votes -
Export metrics to AWS Cloudwatch
Have an integration with AWS Cloudwatch to send the metrics from MongoDB Clusters to Cloudwatch so metrics and alarms can be setup in CW.
14 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
- Don't see your idea?