Feedback

PITR should allow to choose which snapshot to use as base

PITR mechanism does not allow the user to choose which snapshot to use as base before replaying the oplog. Given that Atlas does not validate the snapshots after they have been taken, the user ends up needing to setup their own validation process....

Norberto Leite over 4 years ago in Atlas Backups 0 Submitted

1 VOTE

Improve Metric Correlation

Would be nice to better correlate metrics, server events, and individual operations. For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them ...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

2 VOTE

Delete documents from backups

Allow to delete documents from existing backups based on a query. When off-boarding customers, we sometime need to delete all of their data, including historical data from backups. Having the ability to clean up those backups, without having to r...

Guest over 4 years ago in Atlas Backups 0 Submitted

1 VOTE

Dump audit logs to log analytics workspace

Why can't we dump audit logs to log analytics workspace when we are using azure private endpoints to connect atlas

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

1 VOTE

Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs

We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements. E.g. User is investigating current lags in the data Layer. User has to select al...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

1 VOTE

Incremental backup with reduced snapshots size

The actual size of EACH snapshot is equal to datapath filesystem size. Every snapshot is essentially a copy of all db files. This prevents the use of OPS Manager Backup for large databases. It would be desirable to have a "real" incremental backup...

Guest over 2 years ago in Atlas Backups 0 Submitted

2 VOTE

alerting when a node has a non standard state

Add a new type of alert : to be alerted when one cluster node goes to a state different of standard states ("primary" or "secondary"). For example, I have a cluster that one secondary node is on a transient state : "other". Thank you.

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

2 VOTE

Add Process CPU metrics for `mongos`

Currently the `Process CPU` and `Normalized Process CPU` metrics for all clusters appear to only show the CPU for `mongod`. For sharded clusters, please add a metric to track `mongos` (and possibly `mongot`, for those using it) usage.

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

2 VOTE

allow control of pagerduty urgency (currently high) so that alerts can be managed better

Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

1 VOTE

Specifying who receives notifications for auto-scaling events

Having ability to manage wich roles receive auto-scaling notifications when a cluster scales up or down. Now this is limited to Project Owner but this feature will be helpfull to manage notifications to inform other Team Members wich doesn't have...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Please enter your email address

FILTER BY CATEGORY