Skip to content

Atlas App Services

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

234 results found

  1. Add support for the collection.* metrics to the MongoDB Atlas/Datadog integration

    Currently the MongoDB Atlas integration with Datadog does not support the collection.* metrics.

    As we use Datadog as our monitoring and analytics tool company-wide, we cannot create the needed dashboards unless we create our own app retrieving the metrics and pushing them to Datadog. This is not ideal.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. extend the requirements applied to resource tags.

    We want to extend the requirements applied to resource tags. Right now we have a specific project whose requirements do not allow us to use tag values

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Return the Disk IOPS for advanced GCP clusters through the API (Terraform)

    It would be useful to be able to get the Disk IOPS for advanced GCP clusters through the API (Terraform data block), the same as how the AWS clusters currently work, so that it can be used to set up dynamic thresholds for Write and Read alerts. Currently a value of 0 is returned if it is not an AWS cluster.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Configure refresh token from json deployment files with appservices push

    It would be great if the refresh token could be configured through the 'appservices push' deployment mode in addition to the Admin API.

    It would simplify deployment and would avoid to implement several methods for configuring the application.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Do NOT automatically enable Anonymous Authentication

    It's insanely annoying that enabling developer mode automatically turns on anonymous authentication. If I wanted that on, I would turn it on myself! I frequently use developer mode to deploy non-breaking schema updates by connecting with a new version of my app.

    Moreover, it's just bad form and spaghetti-code to have an option on one panel automatically change options on an entirely different, non-visible panel. LET THE DEVELOPER decide if they want anonymous authentication enabled—I assure you, they know better than you do.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add a refreshCustomData() method to Atlas Functions

    When using Atlas Functions and Role Based Permissions that rely on fields in custom user data, I commonly need to update a user's permissions in the user data, then take some action that requires those permissions - all within the same Atlas Function.

    The current workarounds are to bypass the Role Based Permissions and implement that independently within the Atlas Functions, or return to the client, let the client do a refreshCustomData, then go back to an Atlas Function to continue.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Send tags to Datadog Integration

    We currently use Datadog for our monitoring and alerting. Previously we were using the labels functionality to add information to our clusters in Datadog. With the recent deprecation of labels, we're looking for this same functionality with tags

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Establish communication between the app and the Project Clusters over a Peer-To-Peer network rather than the internet

    We would like to request a change to the data transmition related to Device Sync between Device Sync app and the Project Clusters.

    When both the Device Sync app and the Project Clusters are running on the same Cloud Service Provider such as GCP, syncing with servers should be done over a Peer-To-Peer network rather than the internet.

    This will help make the data transfer be for cost effective and efficient.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Customizable Device Sync alerts

    Currently, when Device Sync is stopped, only one alert is sent out. Other Atlas alerts allow for greater customization, such as resending the alert if the condition persists for a specified amount of time. Because downtime with Device Sync can be disruptive, it would be ideal for the alerts to be repeated.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add error code to SyncException (or a specific Exception for refresh token expired)

    SyncException, inside sync error handler, contains only a string message as public property. In order to identify a specific problem, e.g. refresh token expired, one would need to match a string. In order to avoid that, and make it more robust, it would be great to have a specific error code alongside the message, so one could check the error code and respond accordingly.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Improve Datadog integration

    We're using the Datadog integration for monitoring and alerting. With the monitoring we're having to create custom logic to determine alerting thresholds that are tied to sizes, like connections and memory. We would like additional metrics to be sent to indicate percentage of max for some of these metrics so we can setup our alerts easier.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Triggers - resume via CLI

    Currently the only way to resume a suspended Trigger is via the Admin API:
    https://realm.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/triggers/{triggerId}/resume

    It would be more convenient via the Atlas CLI

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow Customers to subscribe to Atlas App Services Release notes and have them emailed directly to us.

    Allow Customers to subscribe to Atlas App Services Release notes and have them emailed directly to us. Ideally, we would like to have an idea of what is being released a week ahead of time so we can see if any of the new features we can immediately use to accelerate development.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add IP Address BlackList/DisallowList

    Currently, we can only add a whitelist/allowlist IP address ranges which makes it very very hard to just block a specific country or a list of IP addresses.

    The main use case for this is blocking a list of IP Address ranges that are harmful such as if our application is under a DDOS attack or other forms of brute force attacks.

    This is really important to improve the application security and prevent DDOS attacks which in this day and age is very likely for any web/mobile application that has any noticeable traction.

    Services such as Azure already provide such…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Triggers Integration with Azure Event Grid

    We have “Event bridge” integration with Atlas Triggers today. Adding Azure Event Grid support will be very helpful in building no-code solutions like real time sync for ODS/ ODL etc for Azure.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. API for Index

    An API to GET existing indexes in a cluster. The post to create already exists, but I wanted to validate that the index did not yet exist.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Upgrade Node.js version (from v10 to v14/v16)

    It would be great if you can upgrade the version of Node.js used in Realm Functions (currently in version 10.18.1). Version 10.x, which was an LTS, has been unmaintained for many years. The end of life of Node v12 is scheduled for April 2022.

    Is it possible to upgrade Node to version 14 (at least)? Another feature would be to let us choose the Node.js runtime version directly from Realm UI or the CLI (it's possible for example with AWS Lambda).

    Working with Node v10 is really difficult for us since most of the dependencies are not compatible with it.

    67 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    23 comments  ·  Functions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. MFA support

    Enable MultiFactor Authentication in MongoDB App Services authentication. Thus the developers does not need any third party support. They can choose from other Factors (SMS, Whatsapp, E-mail, Push Notification) while selecting the Authentication Providers.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add Null Type Schema Validation to realm-cli

    The realm-cli is already quite powerful in managing the Atlas Apps, but we are missing the setting 'Null Type Schema Validation'.

    In a multi-stage environment, this lead to some environments failing validation while others did not fail.

    The settings should also be included in the realm-cli pull, push and diff command

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 11 12
  • Don't see your idea?

Feedback and Knowledge Base