Feedback

Atlas should raise alert on index build failures

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 want to ensure that index build failures in MongoDB Atlas are not missed. Currently, if an index build fails, Atlas doe...

Jothi Subramani 5 months ago in Atlas Monitoring, Alerts & Observability 0 Future Consideration

2 VOTE

A 2026 suggestion: Help developers think, not just query

Hi Charlie , Thanks for the note, and for building Atlas into something many of us rely on daily. I know this question is going out to a huge developer base, so instead of a feature wishlist, I wanted to share one idea that’s been on my mind as a ...

Zirwa Abid 2 months ago in Atlas Monitoring, Alerts & Observability 1 Will Not Implement

9 VOTE

Add correlated IP address to network access alerts

Hi team, we need to monitor when a specific IP address is added to network access. Now there's an option to monitor this action, however, we are not getting the added IP address in the alert summary or body.

Guest 12 months ago in Atlas Monitoring, Alerts & Observability 0 Submitted

27 VOTE

Prometheus database and collection metrics

We checked the Prometheus metrics provided by MongoDB Atlas and didn't find metrics for the following: Database size Collection storage size Record per collection Indexes per collection Index size We would like to have this kind of metrics to...

Guest about 3 years ago in Atlas Monitoring, Alerts & Observability 3 Planned

50 VOTE

Increase of Functions timeout

Timeout is set to 90 seconds. This value is a fixed setting and is too low for extensive ingestion functions. A default value of 600 seconds would be helpful. Even better would be the ability to set an individual timeout value per application in...

Guest over 6 years ago in Atlas Triggers and Functions 7 Started

41 VOTE

Graph connections per user (or per database)

Show a graph of connections per user. It would be very useful to see how many connections each user has (or also, each db) over time. It would allow us to see more clearly and faster which service uses how many connections.

Guest over 5 years ago in Atlas Monitoring, Alerts & Observability 6 Future Consideration

34 VOTE

Add retry policy to Atlas Trigger

A failed Atlas trigger gets suspended and will not retry without manual intervention. Some transient conditions can be retried and it would be useful to configure a retry policy with a trigger (at the Realm Function level). Retry X times with Y ba...

Charlie Little over 4 years ago in Atlas Triggers and Functions 1 Submitted

11 VOTE

Include Project Activity Feed logs in Atlas Log Integration

With the "Push-Based Log Export" option available in a project, only specific types of logfiles (mongod, mongos and mongod_audit) are being written to the S3 bucket. It would be useful to also have the option of exporting Project Activity Feeds to...

Guest over 1 year ago in Atlas Monitoring, Alerts & Observability 0 Planned

40 VOTE

Splunk connector for Atlas

We need a way to easily ingest logs into Splunk. It needs to be all logs - node and web portal activity. Ideally a Splunk connector would be provided but a stop-gap measure would be the ability to configure Atlas to write all logs to an Azure stor...

Guest almost 6 years ago in Atlas Monitoring, Alerts & Observability 1 Planned

8 VOTE

Collection size metrics

Hi, From time to time we have Atlas auto-scale up our clusters' disks. We then need to start analyzing why. In some cases it is organic growth of the data we store, but in some cases we are missing TTLs or they are misconfigured and we accumulate...

Guest about 1 year ago in Atlas Monitoring, Alerts & Observability 2 Future Consideration

Please enter your email address

FILTER BY CATEGORY