Skip to content

Atlas App Services

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

37 results found

  1. 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)
  2. 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)
  3. Function with Large Memory for Image Processing

    Would be great to set a Scheduled Trigger to process all my database images and store then in S3.

    1— Would need to have memory settings for a function, to specify like 2GB or 4GB.

    2— And ultimately, add Sharp library https://github.com/lovell/sharp because it has install scripts. AFAIK I couldn't install on a local computer then upload to the Realm Dependencies (not tested yet).

    That would create a great dev experience, after a user uploads some images the triggers take over and process all the required image sizes and stores on S3 for delivery over CloudFront.

    Of course, the best…

    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)
  4. Add 'Previously Used' column to table of functions

    Add a column indicating when each function was previously used in the functions screen.

    It would also be helpful to have some basic stats about each functions usage, like total usage count, used in last 30 days, and total usage as a % of all function calls.

    This would help you to find which functions are used most to make them as efficient as possible, and to remove ones that aren't used much.

    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)
  5. Add HTTPMethod column name in Realm HTTP Service webhooks table

    Please add the HTTP method name and other properties in the list of HTTP Service webhooks. See attachment

    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)
  6. Realm UI Ability Changes to Github Repo

    Please add git integration for functions and 3rdParty HTTP services.
    Everything I make a change to a function and it is deployed, Realm tells me what the changes are but they are not pushed to my own Git repository

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

    This was launched earlier last year -https://docs.mongodb.com/realm/manage-apps/deploy/automated/deploy-automatically-with-github/#make-changes-from-the-ui 

  7. Call Functions In Background

    Currently, if you call a function for example function1 from a separate function function2. Function2 will wait for function1 to execute and return before continuing. We have a function that we'd like to use to execute a different function with different parameters, however, the first function has to wait for each function to finish executing before it can call the next one. The first function times out before it can be completed.

    For example:

    function1:
    loop through items in a collection and call function
    2 in a loop

    function_2:
    Some long-running function that takes a while to complete

    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)
  8. 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)
  9. Functions editor support DARK MODE

    Functions editor support DARK MODE

    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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. Support mongoose

    Add mongoose to Functions and a place to store mongoose Schemas,

    Also, Realm UI Schema and authorization documentations are not very complete or clear

    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)
  15. Allow upload of large files through Realm Functions

    Right now we have a 30s input timeout on Realm Functions. We can't upload large files.

    Users in my case uploads large images of 20Mbs, and videos ~50Mb.

    Would be great to see this change, right now we are unable to use Realm for that.

    Also, AWS S3 service has a 4MB limitation as noted here, but not sure, I was able to upload a 7.8MB file https://docs.mongodb.com/realm/services/aws

    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. Availability of Args in Function Context

    Not sure if this is do-able already or not. Couldn't find documentation.

    I have a function that looks like

    exports = function(dbName, collectionName, pipeline){...

    I want to be able to access the arguments sent to the function in the Can Evaluate JSON expression.

    I assumed it might work like

    {
    "%%args.dbName": "eflex-test"
    }

    but that doesn't seem to work

    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)
  17. Access to %%args in Filters

    Allow the access to %%args in filters. This would make it possible to make the apply_when of filters more dynamic by accessing the incoming queries. As of now, filters are completely static due not having access to any incoming information.

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

Feedback and Knowledge Base