Skip to content

Atlas App Services

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

240 results found

  1. One-time scheduled triggers

    At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.

    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

    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)
  2. Need more close realm server in Asia

    currently realm server which can use in Asia is too far and limited like below link
    https://docs.mongodb.com/realm/admin/deployment-models-and-regions/#cloud-deployment-regions
    so, i think it has some delay to request realm server as well as management using realm web UI
    it would be nice to be able to use more close server

    19 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)
    started  ·  Sumedha Mehta responded

    We have started work on more regions as well as cloud providers.

  3. Terraform Provider

    It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.

    13 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. Containerized Functions + Logging + Dependencies Improvements

    I believe most of the below asks would be resolved if you allowed containerized functions to be uploaded and we can have the correct execution environment.
    Allow larger function sizes
    Allow more larger dependency sizes
    Allow 256kb size per log entry
    Allow Unlimited log entries per function execution
    Output formatted logs, don't want to scroll right forever
    Add refresh button for logs
    Log arguments for triggered function automatically
    Don't truncate logs
    Allow logs to be streamed so that you don't need to refresh logs
    Increase execution time to 15-30 minutes
    Allow dependencies to be imported outside of function definition
    Allow…

    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)
  5. GitHub Deploy - pulling deletes standard files, like LICENSE, README.md, etc.

    If I make a change in the UI, deploy, then do a git pull on my local machine, the pull deletes my License, README.md, and .gitignore files. These are standard files and should not be changed on pull. It's like it's overwriting everything from scratch instead of just doing a diff. My repo is public and I need to include this basic info.

    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)
  6. Allow for Name filtering in REALM logs

    Currently Realm logs are pretty limited in functionality. It is hard to sort, filter and track down a specific log file. A filter option based on name would be beneficial. The filter could show all of the recent runs of something based on the name. Also, it would be nice to see the log pages refresh automatically.

    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)
  7. 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 back-off seconds between retries, then fail (plus notification policy).

    31 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)
  8. More Mongo DB actions parity with the Node driver

    The actions available via https://docs.mongodb.com/realm/mongodb/actions/ do not match the API exposed by the Node driver.

    For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#createindex function would be extremely useful for our use case, I can't see any method for programmatically creating indexes via Realm.

    For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#bulkwrite function returns a completely different type from https://docs.mongodb.com/realm/mongodb/actions/collection.bulkWrite/, making unit testing our realm functions locally extremely difficult.

    I'm unsure what reasons there are for this disparity (especially when I can use the mongo node driver to connect locally to an Atlas cluster, but I can't use any of these methods in our deployed application in Realm).

    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)
  9. easily manage single configuration file for different environments for ci/cd

    simply support environment variables expansion in database name or table name
    this way a single configuration folder can be used to configure multiple realm apps
    but each realm app will use a different database/table so the data is separated.
    an official mongodb example code from a blog post about this topic uses this expansion but talking with support they said it is not supported and that the example code is wrong.

    https://github.com/mongodb-developer/realm-demos/blob/main/inventory/export/sync/data_sources/mongodb-atlas/InventoryDemo/InventoryItem/rules.json

    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)
  10. Realm update/replace logs

    I think an enhancement to the realm logs that explains the deltas (what has changed) on a given document for updates/replace would be extremely useful.

    At the moment we receive an ID and the type of change that has happened which is fine for an insert/delete.

    But to understand what has changed on the document for an update/replace would help a lot in diagnosing any issues we have seen with realm in the past.

    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)
  11. Client Side Field-level encryption for Realm Sync

    Support client-side field-level encryption in MongoDB Realm.

    https://docs.mongodb.com/manual/core/security-client-side-encryption/
    https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/

    Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.

    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

    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. views

    Use views (not materialized) as source for realm sync (potentially as read only)

    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)
  13. logs

    When filtering logs I should be able to enter a date/time in the near future for the To date in order to produce a shareable URL in the address bar that will include log lines in the range from some specified date in the past until "now" without having to precisely enter what "now" is.

    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

    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)
  14. Retry function

    We use Realm functions to update related documents in our Mongo Atlas cluster. Sometimes, the DB connection (via context.services.get("mongodb-atlas")) fails. We should... be able to retry establishing a connection? (Or even easier, just configure a retry for the Realm Function itself.)

    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

    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)
  15. External Dependencies Should Be Per Function

    10mb compressed size constraint is very limited. Plus, dependencies are not siloed per function. Either uncap the dependencies constraint or allow dependencies to be uploaded per function, still with a higher compressed size constraint (preferably at least 100mb to support large dependencies such as for image processing).

    I think the thought was "functions are meant to be short running operations" but I think that is a huge assumption. Why not offer options for powerful compute that respond to database change events. Sure you may need to just update something else in the db, and that may be sufficient for some…

    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)
  16. Programmatic Support for Uploading Dependencies

    Right now the Realm Administration APIs [1] only let's users list dependencies. It would be helpful to have an endpoint to upload dependencies as we have 8 env and uploading manually to all envs is painful.

    [1] https://docs.mongodb.com/realm/admin/api/v3/#dependency-apis

    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)
  17. Migrate Firebase Cloud Message from legacy HTTP to HTTP v1

    I am very happy with Push Notifications using FCM but currently, FCM has been update to HTTP v1 and I saw that MongoDB Push Notification still using the HTTP. With HTTP, I can't send an image in the notification payload (https://firebase.google.com/docs/cloud-messaging/android/send-image), also the data payload is different when I send message directly from FCM.

    I hope that MongoDB have plan to migrate Firebase Cloud Message from legacy HTTP to HTTP v1 (https://firebase.google.com/docs/cloud-messaging/migrate-v1)

    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. Customize Reset Password Email Link

    Users should be able to customize the reset password email that is sent to their users. This should include changing what the "sender" url looks like (noreply-stitch+mongodb.com => resetPassword@yourapp.com). Developers should have access to change look of the body of the email. This includes what is typed in the body, the title of the body and as well the company logo. I will upload a picture of how it currently looks and from my message understand what we want to change.

    8 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)
  19. Selective Realm Reset

    We are running Realm Sync from an iOS app (RealmSwift 10.7.2). We have a problem where the data related to one Realm partition is giving is a BAD CHANGESET error in production due to a data
    issue. My suggestion is, can we cancel Realm Sync operations for a particular partition as opposed to terminating the sync for the entire app (all partitions) which would force all of our users to reinstall their apps so a fresh local copy of the Realmfile is built)? We don't want to be resetting across all partitions because it impacts all production users and in…

    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)
  20. Build system for static hosted SPA

    Currently I use Netlify for static hosting, which will run a build script when I push a commit. This simplifies my deployment process. It would be useful to have an equivalent for Realm static hosting.

    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)
  • Don't see your idea?

Feedback and Knowledge Base