Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
181 results found
-
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 -
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.
5 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 -
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 -
Show node region on the metrics tab
It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.
2 votes -
Separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster
This is a request to separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster
4 votes -
Disk Usage Breakdown
When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.
2 votes -
Allow default settings on alerts on project/organization level
It would be great if there was a way to set the default notification channels for alerts on the project and organization level.
I was recently informed by the support team that there is no possible way of doing so, and that all alerts should be changed individually rather than for the whole project in one go.
1 vote -
eviction metrics
Please include eviction metrics as well in monitored metrics in atlas so that it will provide an overview how many evictions are happening in particular time and there by decide correct memory for the instance.
1 vote -
Invoice: Ability to post items to a collection daily
You have daily line items on invoices. It would be great to be able to configure our billing to post to one of our collections. This would allow me to put charts on top of usage across all of our project and not just monthly
2 votes -
Separate metric graphs of egress outside the region per database, collection, user, destination
Separate metric graphs of egress outside the region per database, collection, user, destination, so that I can easily find out what is causing the egress traffic which is billed on my account. This will also help me identify what parts could be good to move to different cluster in another region closer to the user,
1 vote -
More granular results in Activity Feed
I can't see all the data I want today
1 vote -
Metrics "seconds" improvement
The uppercase "S" on the metrics which indicates seconds, can be slightly misleading as it can appear to be the number 5 when placed next to another number. This is especially misleading on the Replication Lag metric. It may be easer to read as a lowercase "s" or abbreviating with "sec".
2 votes -
Expose OAuth2 for Slack integration to API
I think to have the third party integrations as Terraform resources would be ideal, but currently the Slack integrations supports OAuth2 via UI and not via API. It would be good to be able to configure this through the API, so that this can be automated.
1 vote -
Add eventTypeName for Maintenance Windows in alertConfigs response
After adding a maintenance window to an Atlas project, the alertConfigs returns additional entries that do not include an eventTypeName field, it seems that these additional entries relate to the maintenance window but it's not clear:
{
"created" : "2020-02-28T16:04:18Z",
"enabled" : true,
"groupId" : "",
"id" : "",
"links" : [ {
"href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe",
"rel" : "self"
} ],
"matchers" : [ ],
"notifications" : [ {
"delayMin" : 0,
"emailEnabled" : true,
"intervalMin" : 60,
"roles" : [ "GROUPOWNER" ],
"smsEnabled" : false,
"typeName" : "GROUP"
} ],
"updated" : "2020-02-28T16:04:18Z"
},…1 vote -
1 vote
- Don't see your idea?