Feedback

Add setOnUpdate operator for Upsert operations

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We regularly want to upsert documents to mongo, and include a useful createdAt and updatedAt timestamp. createdAt is easy:...

WelcomeLend Operations 3 months ago in Querying & Aggregations 1 Future Consideration

20 VOTE

Show max IOPS line on IOPS graphs

When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.

Guest over 5 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

20 VOTE

Automatic information when shared cluster is throttled

When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting. Right now there is no way for a db-owner ...

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

23 VOTE

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.

Guest over 6 years ago in Atlas Monitoring, Alerts & Observability 3 Started

12 VOTE

Nanosecond timestamp support

I've put this under the time series category since that's where it's most applicable, but it's really a data model / BSON issue. The topic of higher resolution timestamps have been surfaced from time to time for at least a decade (https://jira.mo...

Guest over 3 years ago in Database 1 Submitted

18 VOTE

Support node type or node tags as condition in MongoDB Atlas Alert

Currently, the MongoDB Atlas does not support the node types [1] or node tags [2] as the condition in Atlas alerts. That would be super inconvenient for the following scenarios. Scenario 1: If the user wants to create an alert to monitor the spec...

Guest almost 5 years ago in Atlas Monitoring, Alerts & Observability 0 Started

10 VOTE

Change Streams Monitoring and Alerting

Change streams can cause performance issues if not used properly. In some cases, administrators of multi-tenant dbs have no control (and shouldn't) over how various clients create change streams. I think it is important that we accommodate these...

Guest almost 3 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

14 VOTE

Make it possible to delete a database via API

It would be nice to be able to delete a database in a replica set via an API call. This would make it easier for CI/CD when deleting clients Strange thing is that I can delete a complete cluster, but more fine-grained deletion is not possible. lik...

Guest almost 4 years ago in Database 1 Submitted

2 VOTE

Per-Shard Change Stream and Triggers to improve scalable/performance/resilience

In our geo-sharded cluster, we use Change Streams and Atlas Triggers. Most of our pipelines include a match for the shard key - so we can process the data in the same region where the data resides. However, due to the design of change streams wit...

Boris Figovsky 7 months ago in Database / Replication & Sharding 1 Submitted

21 VOTE

Email subject more specific for Alerts

The email Alerts that MongoDB provide are very useful, especially the Oplog and CPU Usage. However, the subject of the emails are not clear and does not specify the Alert type. It is just a generic "Alert". It would be great if MongoDB can add "Al...

Guest almost 6 years ago in Atlas Monitoring, Alerts & Observability 4 Submitted

Please enter your email address

FILTER BY CATEGORY