Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Feedback

Showing 358 of 4027

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

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

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

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

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

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

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

python

Python support would be great to allow us to have a single code base
Guest about 5 years ago in Atlas Triggers and Functions 0 Submitted

Add the ability to trigger alerts for testing purposes

It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.
Stephen Jamieson over 5 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

Incorporate Resource Tags in Atlas alerts

Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted