Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
168 results found
-
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 -
CPU Steal % on Azure
The CPU Steal % metric and alert seems to be currently implemented only for AWS. Please implement it also on Azure, as there is no easy way currently to get alerted if the underlying burstable VM (e.g. for M20) runs out of credits ...
2 votes -
Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale
Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale
Currently, when a mouse is not hovering over a Metrics plot, the plot will show particular hours as labels for the x-axis. For example, if an 8 hour range of time is displayed, the time every two hours will be labeled.
However, if more than 1 day is displayed, the x-axis labels are less useful. The particular time once/day is displayed, but the day is not included. For example, when I display a week of data, 07:00 is highlighted on each particular day,…
2 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 -
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 -
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 -
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-0Now 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-0This 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,…2 votes -
2 votes
-
Monitoring Integration with Azure Event Grid
Monitoring Integration with Azure Event Grid.
2 votes -
Database Access History: sort and export
Would be nice to export the database access history and/or sort by a column.
2 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 -
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 -
Don't cut alert names
This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.
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 -
Allow tagging of mongo atlas alarms
It would be awesome to have possibility to tag alerts in atlas when creating using API or console. It will allow to process groups by alerts by tags without keeping track of ids.
requires:
adding tag field to API create call
adding query by tag to API delete or update calls.Pavel
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 -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 votes -
Disk throughput in monitoring
Currently we have disk IOPS in monitoring (both read and write).
One of the metrics that play a role to decide whether to have a provisioned disk or not, at least with AWS hosting, is the disk bandwidth.
For instance with a large enough disk, like 2000GB, I have max 250MB/s bandwidth with an unprovisioned (gp2) disk (the maximum), but could go to 500MB/s with a provisioned (io1) disk of that size.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
- Don't see your idea?