1365 results found

1. U domain Verification

   If you are able to verify the parent domain for your company, then you shouldn't need to have to verify the sub-domains associated with that domain. Company's do not generally advertise their internal u-domains on the internet therefore any verification on that sub-domain will naturally fail. This is hindering us from integrating our Okta credentials with our login information.

   •  

   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  ·  IAM  ·  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. Disable (or warn about) destructive features

   We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

   It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

   For example, these features are rarely if ever used in our production environment:

   • db.collection.drop()
   • db.collection.remove() or db.colletion.deleteMany(), especially if the query is empty or results in a very large number of documents
   • db.collection.dropIndex() and db.collection.dropIndexes() -- the "Require Indexes for All Queries" setting is too late to catch this
   • $out operator (and perhaps $merge as well) in aggregation pipelines.

   Of those, only $out is somewhat covered: MongoDB Atlas Data Explorer's aggregation query warns the user before executing a pipeline that ends in a $out stage. mongosh has no similar warning.

   We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

   It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

   For example, these features… more

   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  ·  Data API  ·  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. Feature: Atlas UI -- Star/Favorite/Bookmark of Project

   It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search

   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 EventBridge integration for Serverless instances

   Currently EventBridge integration doesn't work for serverless instances

   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  ·  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

5. Support exporting Custom routes

   Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
   We have peering with other product and they support it !

   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

6. Restore indexes from AWS S3 snapshot.

   While working with export snapshot to AWS S3, I found there is no way to restore indexes from metadata.json, along with data there must be opportunity to restore indexes as well otherwise have to rely on custom solutions and this may include external dependencies.

   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  ·  Backup  ·  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. Send alert(email) when database is deleted

   The alert conditions do not contain conditions like
   - when database is deleted
   - when cluster is deleted
   - when project is deleted

   We want to get notified if a malicious person or someone by mistake deleted major parts of the database.
   This simple notification is not possible right now.

   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

8. Add hint support for MongoDB API functions

   The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.

   However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.

   I think that "hint" is a great "backup" feature for cases where the Query Planner selects the wrong index and you cannot afford to hide that index for some reason.

   The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.

   However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.

   I think that "hint" is a great "backup" feature for cases where… more

   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

9. Accept VPC peering connection when created by MongoDB::Atlas::NetworkPeering

   VPC peering connection created by CloudFormation resource MongoDB::Atlas::NetworkPeering have to accepted in AWS, using GUI, CLI etc. Would that be possible to get this done using CF only?

   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  ·  CloudFormation Resources  ·  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. Alert when Database users count reaches a threshold for example 60
    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  ·  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

11. Query Online Archive over Web UI

    There is currently no possibilty to query a collection of an Online Archive via the Web UI of Atlas. This is only possible for the "normal" collections.
    It would be great if it would be possible to also query Online Archivce collections similar.

    This is related to the request of https://feedback.mongodb.com/forums/924277-data-federation-and-data-lake/suggestions/40949902-access-online-archive-in-customer-data-lake

    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  ·  Online Archive  ·  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. API for slowQueryLogs should give response in a proper json format like in UI

    API for slowQueryLogs should give response in a proper json format like in UI rather than giving raw logs

    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  ·  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

13. Allow access to Admin API using AWS IAM role

    It's possible to authenticate to a database using AWS IAM role. The same should be possible for the Admin API.

    The problem with the API keys is that they can be taken away and used elsewhere. They pose an additional risk in an AWS integrated environment.

    This also relates to upcoming Cloudformation Resources where the extension needs to store the API Key in AWS Secrets Manager. The resource already has a role that could simply be configured to be trusted on the Atlas side.

    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

14. GCP eu-southwest-1 Madrid Atlas region

    Would love to deploy the cluster in the recent GCP eu-southwest-1 region. It is already running, and would be a plus for all Spanish customers reducing latency. It does not yet appear in the Atlas cluster creation page.

    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  ·  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

15. Get all databases from one cluster

    Add a new Admin API to Atlas: Get all databases from one cluster

    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

16. show the reason why you can't increase oplog

    in the settings=>additional settings=>More Configuration Options=>Set Oplog Size
    show the reason why you can't increase this parameter (let's say you have insufficient free space etc.)

    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

17. Prometheus metrics formatting to match Grafana

    Building on "Export metrics to Prometheus" (marked as completed) https://feedback.mongodb.com/forums/924145-atlas/suggestions/40463872-export-metrics-to-prometheus

    I have configured the Prometheus metrics integration to make metrics available to Grafana Cloud which has a MongoDB Integration built in. I was disappointed to see that most of the metric names don't match the ones expected by the MongoDB Integration in Grafana.

    The MongoDB documentation doesn't define a standard metric nameset so I appreciate that this is nominally correct behaviour, but it would be good to see some consistency between the MongoDB Atlas integration and the metrics expected by Grafana.

    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  ·  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

18. When Adding new CKM key/role Atlas should validate if it can safely change existing CKM key

    When we create new CKM key with new role and update credentials on project level, Atlas validates that new role can read new key. But it does not validate if new role can read existing CKM key.

    When Atlas starts re-encrypting existing cluster, first node goes down but can't be started because new role can't read old key. There is no way to restore/rollback this change unless raise a ticket for MongoDB support.

    Suggestion: when we upgrade credentials/role/KMS key in UI, Atlas should validate if it can finish this change BEFORE applying changes to nodes.

    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

19. Atlas UI enhancement

    Hi,

    Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.

    1. When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
    2. Right side top corner, we can also see it states "All Clusters"
    3. Terraform resources/attributes talks about Clusters
    4. Only place we see in the home page "Database Deployments"

    Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in single "Database Deployments/Clusters" , it would be helpful it can be changed it back to Clusters instead of "Database Deployments" to align with other places. This will help customers more clarity.

    Thanks,
    Suresh

    Hi,

    Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.

    1. When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
    2. Right side top corner, we can also see it states "All Clusters"
    3. Terraform resources/attributes talks about Clusters
    4. Only place we see in the home page "Database Deployments"

    Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in… more

    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

20. Support serverless OLAP workloads

    I can use scondaries to support OLAP workloads however I'd like autoscale read-only and analytic nodes using the serverless cost model.

    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  ·  Serverless Instances  ·  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