Feedback

This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Managed Grafana instance

This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Grafana Managed Instance. Azure Managed Grafana instance has Enterprise plugin for MongoDB but that is a Market place product which is not available to customers...

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

5 VOTE

Ability to set Values in Functions

Ability from webhooks and functions to call context.values.set() and set a value that can then be referenced somewhere later. This could dramatically cut back on calls to outside APIs as we need data in multiple places so we end up having to make ...

Guest almost 8 years ago in Atlas Triggers and Functions 0 Submitted

2 VOTE

Support Multiple CRON Schedules Per Trigger

It's not uncommon to want different trigger schedules to run on different days of the week, notably weekdays and weekends. The current solution is to create separate triggers that call the same function, but ideally, a single trigger could support...

Guest about 3 years ago in Atlas Triggers and Functions 1 Submitted

2 VOTE

Triggers on DB level rather than single collections only

Change streams support events on DB level *or* single collections, but triggers are limited to single collections. Which means that if we wanted to listen on changes in a generic way, we would have to setup a trigger for each collection and set th...

Guest about 3 years ago in Atlas Triggers and Functions 0 Planned

1 VOTE

Alerts on password reset in Atlas UI

Alert should be sent on specific accounts in case of reset is initiated from Atlas UI.

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

3 VOTE

alerts on specific database

I'd like to setup an alert on my cluster for specific database but currently I can only setup alerts for all databases on my cluster. for example, send alerts when "Document Metrics: Deleted above 1" on zyz database

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

2 VOTE

Meaningful errors

Descriptive errors are crucial for debugging and simply cannot be found with Atlas App Services ! 1) If an error occurs - the whole function cascade is terminated - not only the steps following the error but also the ones prior to it. i.e. if a co...

Guest over 3 years ago in Atlas Triggers and Functions 0 Submitted

2 VOTE

Send alert(email) when database is deleted

The alert conditions do not contain conditions like - when database is deleted - when cluster is deleted - when project is deleted We want to get notified if a malicious person or someone by mistake deleted major parts of the database. This si...

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

3 VOTE

Display the Atlas-generated replica-set name in the cluster Dashboard

This is an easy one, and it'll help a lot. Inconvenience: ============ In the past, every time I created a cluster, the name of the replica-set was in line with the name of the cluster: e.g.: Cluster Name: `asteroids-tracking` Replicaset Name: `...

Guest about 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

1 VOTE

Call Functions In Background

Currently, if you call a function for example function_1 from a separate function function_2. Function_2 will wait for function_1 to execute and return before continuing. We have a function that we'd like to use to execute a different function wit...

Guest over 1 year ago in Atlas Triggers and Functions 0 Submitted

Please enter your email address

FILTER BY CATEGORY