Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
169 results found
-
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 -
Export profiler slow queries via Datadog integration
The "profiler" tab in Atlas is very nice -- it gives a really nice over-all view of slow queries, with the ability to drill down into the individual calls.
However, I don't check this page every day, and so it is sometimes hard to find out when we actually do have slow queries or commands pop up on it if it is not affecting our cluster.
We use datadog as the central point for all of our monitoring. We have the Atlas <--> Datadog integration set up, which exports a number of useful stats. It would be very nice for…
3 votes -
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 -
Integrated/unique metrics vision for primary replica-set
It is really hard to understand the behaviour of primary replica-set on bigger timeframes, when it was switched some times. Would be very helpful to be able to see the metrics in a integrated chart, to understand consequences of some actions like application changes, index creations, version upgrades, etc.
1 vote -
Add metrics to monitor CPU credits for burstable performance Atlas clusters
Add metrics to Atlas for tracking burstable CPU credit spend for M10 and M20 cluster tier instances. Additional add support for creating alerts based on these metrics.
10 votes -
Display Total Cluster Data Size in Atlas UI
Atlas doesn't display the total data size of the databases hosted on the sharded cluster. This feature was available in Opsmanager and will be very helpful for the DBA's and the product development teams to glance at the data size of the cluster.
Attached the screenshot for example.
Nice to have or display the size of each database and also display the historical datasize metric for each database in a sharded cluster.
3 votes -
Metric Charts Aggregated by Primary Node at the Time
Providing an aggregated metrics based on the primary server. Right now in order to view history for the primary we have to compare the different charts based on failover, makes it cumbersome to view the active primary trends
1 vote -
Use additional metadata to differentiate processes
Right now Ops Manager monitoring identifies MongoDB processes according to hostname:port. Unfortunately, if 2 processes have the same short hostname & port in the same Ops Manager project, they'll be treated the same even if they are actually different processes with different FQDN.
Please either allow the use of additional characteristics (FQDN, replica set name, config server name, etc) for differentiating MongoDB processes or provide some way to tag 2 or more processes so monitoring doesn't accidentally miscategorize them as the same process.
2 votes -
Minimum Oplog Retention Period - Set Minimum Oplog Window
The documentation states: "New in version 4.4: Starting in MongoDB 4.4, you can specify the minimum number of hours to preserve an oplog entry." https://www.mongodb.com/docs/manual/core/replica-set-oplog/#minimum-oplog-retention-period
The mongodbatlas_cluster resource in the terraform mongodbatlas provider only provides for the oplog_size_mb argument. https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cluster#oplog_size_mb
It would be nice to have that exposed so that terraform can update that value.
1 vote -
Metric on TTLDeleted documents
Hi,
We (Indeed, inc.) are one of your larger customers with more than $2M spend on Atlas in a year. We need a metric on number of TTL Deleted documents per second for an Atlas Cluster. We have similar metric on our standard mongodb plugin in Datadog and this is extremely useful to all our Product Teams because most of our clusters have TTL.
Thanks.3 votes -
Basic operational metrix support with instana and grafana
Hi MongoDB Team,
We are using grafana and instana SRE tools for application monitoring.
But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .
Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.
I would request you to prioritize this request since lack of these reports is creating an empty space…
1 vote -
prometh
Hi MongoDB Team,
We are using grafana and instana SRE tools for application monitoring.
But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .
Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.
I would request you to prioritize this request since lack of these reports is creating an empty space…
1 vote -
Display replica set members' Availability Zone details
The AZ details (ideally including the AZ ID) for each replica set member would be helpful to display in the Atlas UI, mainly to easily verify nodes are distributed across AZs.
45 votesThank you all for your feedback!
We hear you loud and clear and are working on exposing these details in the next quarter.
-
Save ATLAS monitoring selection settings
Atlas monitoring has different setinngs: Primaries, Secondaries, All
it would be good if the setting ALL (and maybe others) could be saved so I do not need to select it again.
thanks
Rene Schwarz1 vote -
Expose Locking Metrics
One of our customers have asked if we can expose locking metrics through the Atlas UI to assist with investigating suspected lock contention issues.
We have this information in FTDC and our customer feels it would be helpful for them to have this information too.
4 votes -
Last Database User Access
My team has found ourselves in the position of needing to iterate through the Database Access History Logs in order to discover whether or not a database user is still being used for the past t time periods.
We need to have this functionality in order to guarantee a seamless credential rotation.
With the current API this operation will require iterating over each cluster's access logs for the past t time periods. If I have "n" clusters and "t" time periods this is an O(n * t) runtime. I'm not really great at O() notation, but if t is greater…
4 votes -
Add support for HTTP based scraping without IP restriction
Prometheus supports a lot in the HTTP scraping space, including oauth and Bearer token based scrape targets.
Currently we use Grafana cloud that has a list of IP address that can scrape from. This "can" change, and if it does and we hardcode this access into Atlas based on IP then it will break the scrape.
Could Mongo add support for token/oauth based scraping. Where we provide these tokens in a HTTPS call?
I think this would solve the issues with things like private link, or peered network connections. It would also allow "any" prometheus server that can make outbound…
2 votes -
Allow switching between shards in the profiler and/or have a combined view
Since the profiler tabs are shard specific, it would radically improve the usability to:
a) Combine the profiler events to truly have a cluster level view so you don’t need to worry about shard specific views
b) Add a drop-down to the top of the page near the title that has the various shards listed in it, selecting a different shard brings you back to the same tab, but now with the changed view.
c) Consider tweaking the URL so that rather than using a SHA in the URL, you use the shard name, making it easy to manipulate the…2 votes -
Support export Prometheus metrics via remote_write
High throughput prometheus compatible database like mimir, thanos, and the likes of GCP's managed prometheus really like metrics sent to them via remotewrite https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remotewrite. Grafana cloud for instance doesn't allow you to configure any scrape rules. The only option is to push metrics to them.
Currently Atlas only allows you to scrape metrics, which means for a user to get these metrics into a highly available version of Prometheus you need to relay this off of an intermediary process (prometheus exporter or a standalone prometheus server that supports scraping)
I think a good addition to this capability would…
1 vote -
Allow the image export using Atlas Admin API
For the report purpose, we need to get the exported images of Status/Hardware/DBStast.
With personal authentication, I can get these images via URL:
https://cloud.mongodb.com/export/v2/charts/{status/hardware/dbstast}/{clusterID}/{hostID}/{format}/{title}?since={since}&until={until}&hostDbStatsName={DBName}However, I cannot get it programmatically with API Key authentication.
Let's allow the image export using Atlas Admin API.
Thanks!3 votes
- Don't see your idea?