Skip to content

Divyansh

← MongoDB Feedback Engine

My feedback

6 results found

  1. Atlas metrics granularity after 48 hours

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Monitoring and Metrics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Divyansh commented  · 

    Very important. This will make analysing past issues much easier. It's actually a huge point of contention while interacting with support.

    Divyansh supported this idea  · 

  2. Scaling cluster connections independent of cluster size/tier

    17 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Atlas » Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Divyansh commented  · 

    "Unfortunately larger and larger numbers of connections require more compute" We understand that and there's a difference in compute ability between M10 and M20 already, that's why we have them as different tiers. So ideally, the number of connections available in M20 should be higher as well.

    Also, can you clarify if the number of connections is an altas-level limitation or a cloud provider-side limitation? If it's a cloud provider-side limitation, which instance type are we using in AWS? Because I've not experienced the same in mongo on-prem deployments.

    Divyansh supported this idea  · 

  3. Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Divyansh commented  · 

    This is very important, we don't even have a view in atlas to search by replicaset name!

    Divyansh supported this idea  · 

  4. Granular cost and inventory details

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Atlas » Billing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Divyansh shared this idea  · 

  5. Need granular export details while exporting cloud backup to aws

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Atlas » Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Divyansh supported this idea  · 

  6. Create distinct indexes for Analytics nodes

    39 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    6 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Divyansh supported this idea  · 

Feedback and Knowledge Base

(thinking…)