1366 results found

1. docsexamined

   in profile tab, there are only keysexamined, nreturned we can see.
   If we have "docsexamined" , it would be good to check whether the queries are well tuned or not at first glance.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. mongomirror with db rename

   We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.

   Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.

   But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add Process CPU metrics for `mongos`

   Currently the Process CPU and Normalized Process CPU metrics for all clusters appear to only show the CPU for mongod. For sharded clusters, please add a metric to track mongos (and possibly mongot, for those using it) usage.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Allow Performance Advisor reporting export

   Having the ability to extract/export the Performance Advisor report. This would allow users to share a file with others who may not have access to Mongo Atlas.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Performance Advisor  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. allow control of pagerduty urgency (currently high) so that alerts can be managed better

   Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Alerts  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Delete one (last)endpoint deletes private endpoint service

   If no further endpoint is associated with Private endpoint service, making a call to api resource https://docs.atlas.mongodb.com/reference/api/private-endpoints-endpoint-delete-one/ will delete the endpoint as well as service.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. payment

   Add PIX payment method. I don't know how much of a hassle it's to implement such payment method for brazillians, but I think it would be one of the "killer feature" for us. Thank you.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. I'd like the ability to be on premise and burst into Atlas when needed.

   As an system administrator running MongoDB EA, I'd like the ability to be on premise and burst into Atlas when needed.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Support optional fallback to source cluster after cutover in Live Migration

    Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.

    It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.

    Having a "fallback sync" option could help with this.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Allow auto-scale for IOPS.

    Allow auto-scale for IOPS.

    50 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Autoscaling  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. killAllSessionsByPattern and kill sessions

    Please add killAllSessionsByPattern and kill sessions feature in Atlas UI

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Add date added and date updated to Network Access IP table

    The network access table should have a way to see the date an IP was added and if/when is was last updated. This will give better insight and control over company users add and maintain their IPs when only whitelisted access is allowed.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Show driver/application/user metadata in Query Profiler query summaries

    It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.

    After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.

    This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).

    This information could then help pinpoint the source of the query so it can be adjusted if need be.

    It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.

    After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.

    This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).

    This information… more

    35 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add "scheduled scaling/suspend" option for certain clusters

    There should be an option to schedule scale up/down or suspending/resuming at specified time & day.

    For example, DEV environments could be auto-suspended at 6pm and resume at 8am on weekdays, and be suspended all weekend.

    Production clusters could be scaled down e.g. from M80->M60 every evening and on weekends rather than being suspended completely.

    This would help save money but would need to be coordinated with the existing auto-scaling based on load.

    This would need to be at the cluster level since sometimes different clusters in a single project could have different workload patterns.

    37 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Autoscaling  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Discord Integration

    Hi, I would like to know if there is a possibility to deploy Discord (webhook) integration like Slack.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. To modify transactionLifetimeLimitSeconds parameter

    As this is one of the most common request from Atlas customers to modify transactionLifetimeLimitSeconds it would be beneficial to grant the privilege so the Atlas customers are able change this parameter within a certain limit. Please add this functionality.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Make AWS EBS Burst Balance metrics available in Atlas UI

    Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.
    
    You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Allow domain or URL for whitelisting

    Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Unpause Cluster for X Duration

    Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.

    Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours

    Current Atlas Control Plane: "Pause Cluster"

    Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"

    This is similar to how customers can create temporary database users that are only active for X number of hours. If cluster is already paused, then Automation would simply log that cluster was already paused, and no automated pausing was required.

    Functionality should also be built into the following request:
    https://feedback.mongodb.com/forums/924145-atlas/suggestions/42126274-set-schedules-for-pausing-clusters

    Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.

    Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours

    Current Atlas Control Plane: "Pause Cluster"

    Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"

    This is similar to how customers can create temporary database users that are only active for X number of hours.… more

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating