Skip to content

Atlas App Services

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

262 results found

  1. Allowed Request Origins should support URLs with wildcard characters

    The Allowed Request Origins list in the App Settings, at this time, doesn't support URLs with wildcard characters. As modern services like Vercel generate dynamically new URLs during development, the list needs to be updated every time with the current URL, while having an option available that would accept "https://*-myappname.vercel.app/" would simplify that step.

    5 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. Trigger event queue metrics

    We recently ran into the problem that our trigger was suspended because the resume token was no longer present in the oplog.
    The problem was a combination of queued up trigger events and a short oplog window and the suggested solution was to increase the triggers performance by parallelizing it and by increasing the oplog size to get a bigger oplog window.

    Unfortunately, we're not able to verify the real success of these suggestions, because even though we can monitor the oplog window in the metrics, there are no metrics for the trigger queue itself. As a result, we can't…

    5 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. Add support for GitLab

    As an alternative to using GitHub

    5 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. Increase RealmReturn Body Max Size

    The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
    It requires the client to make many more requests that would be necessary.

    In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).

    Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…

    5 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)
    planned  ·  Drew responded

    Hi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.

  5. nodemailer Support

    Nodemailer is currently not supported because of the punycode dependency. Would be nice to send mails directly on the mongodb server.

    5 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)
  6. Passwordless authentication provider

    Passwordless logins are quite commons nowadays. Firebase supports "Login with email link" (https://firebase.google.com/docs/auth/web/email-link-auth). Would be nice to have the same in Realm.

    5 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. Allow editing of the generated GraphQL schema and resolver

    The data model that I want to expose to the user is not the one that I have in MongoDB, having this feature would be nice

    5 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  ·  GraphQL API  ·  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. GraphQL in Realm Functions

    It would be useful to have an integrated GraphQL client that is authenticated against the cluster available in Realm functions, to create stored queries and modify these in postprocessing in a Realm function.

    5 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  ·  GraphQL API  ·  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. Schema for Realm's JSON Files to Enable Auto-Completion

    This is a minor suggestion but it will be great if intellisense works for Realm-specific json files (i.e. "auth_providers/api-key.json", "services/mongodb-atlas/rules/db.collection.json", etc).

    It will be helpful for developers using the Ream's "Deploy with CLI/GitHub" feature (which is great). I guess it may help reduce confusions; for example ObjectId/ObjectID/objectId.

    VSCode has built-in support for JSON schema, and it seems additional schemas can be specified via three options: $schema in the file, VSCode settings or an extension.
    https://code.visualstudio.com/Docs/languages/json#_json-schemas-and-settings

    5 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. Default value for fields

    A way to set default value to a field, when this is not given in the input.

    GraphQl already has this functionality..

    5 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  ·  GraphQL API  ·  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. Copy functions from one cluster to another

    It would be great if you could copy a Realm Service or Function from one cluster to another. I find myself having to open two tabs and coping the function code then checking all settings are the same etc.
    We would normally dev on a "test" cluster then copy Service functions over to "prod" cluster. Or am I missing something?

    5 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)
  12. Ability to Reuse Types in Custom Resolver Schemas

    We are in the process of migrating from a hand-implemented Apollo server to Mongo Realm, but are finding the inability to reuse types on custom resolvers to be a serious impediment.

    For example, we have a number of custom resolvers that use the same type to define a temporal interval, but we cannot reuse that type in the arguments for our custom resolvers as Stitch will throw an error upon encountering those duplicated types. Additionally, many of these custom resolvers return the exact same type, but if we try to reuse that same type definition Stitch will throw errors about…

    5 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

    2 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    planned  ·  Drew responded

    Hi Folks – This improvement is already planned and should be completed shortly.

  13. 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 several calls.

    5 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. 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)
  15. 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.

    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)
  16. Account Level Functions, Triggers and Values

    Can you please add the option to mark a 'Function, 'Trigger' and 'Values' to be available beyond a Realm App?

    That is, global type option for a Cluster and Account. This way we do not have to keep redundant copies. This is important for multiple Realm Apps, development & testing, etc.

    Thank You!

    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)
  17. List databases and collections from Atlas data api

    Ability to discover databases and their collections from the Atlas data api.

    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)
  18. 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)
  19. Support for JSON schema oneOf / anyOf / allOf

    In our current project we have the requirement to support slightly differently shaped documents, contained within in the same collection, that are identified by an enumerated "type" field. In order to do this we require the ability to make use of the oneOf / anyOf / allOf polymorphic features of the JSON schema which would then ideally be relflected in the MongoDB Realm GraphQL endpoint. I was informed that this was being looked at a while ago but can see no associated feature request.

    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

    0 comments  ·  GraphQL API  ·  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. Please write explicit rules for anonymous auth users deletion or provide controls to adjust the behavior

    In the documentation for anonymous auth, it says that Realm may delete anonymous users that are 90 days old https://docs.mongodb.com/realm/authentication/anonymous/

    There is also a mention about 30 days of inactivity https://developer.mongodb.com/community/forums/t/persisting-anonymous-users/10247/2?u=anton_p

    That's hard to rely on something so broad to make decisions in the app logic. Is it possible to clarify this behavior or provide control over this flow?

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

Feedback and Knowledge Base