Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Increase monitoring metrics resolution retention time on views of 1min & 5mins

    The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.

    After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.

    I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.

    10 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  2. Alerts Messaging Customization

    At the moment, it appears one cannot customize the messaging or subject line of the alerts. This makes it difficult to categorize the alerts. For instance, we would like to categorize alerts into different severity levels, such that severity level will help determine the level of attention that is paid to the alerts when they trigger. If it is possible to prefix or append some customization code and message to either the subject line and/or actual message, then a monitoring team can use the custom code/message to determine the severity or category of the alert when it triggers.
    Some alerts…

    12 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

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  3. Include Human-Friendly Cluster Names in Alert Notifications

    Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).

    9 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  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.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  5. Profiler chart scale

    In the profiler page, the charts scale do not make sense.
    The maximum values in the Y axis are very high which make the investigation very difficult if the actual values are smaller.
    I suggest that Y axis values would be dynamic to each the research.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  6. track collection size

    I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?

    3 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    10 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  8. Show BI Connector resource use Metrics

    It would be helpful to be able to view the resources used by the BI connector in Metrics, similar to how you can view resources used by Atlas Search (Search Disk Space Used, Search Normalized Process CPU, etc). This could help with identifying issues due to resource intensive queries submitted through the BI connector.

    Currently it is only possible to guess that an issue could be related to the BI Connector by viewing system resource use.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  9. killAllSessionsByPattern and kill sessions

    Please add killAllSessionsByPattern and kill sessions feature in Atlas UI

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  10. audit log event when new project is created in an organization

    add an audit log even when any user within the organization creates a new project. Currently you can see when a collection is created, but nothing for new projects. This is helpful for auditing and accountability purposes.

    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

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  11. separate resources for monitoring function agent and database

    To change the resources monitoring function agents which is currently using Shared resources, we prefer it to be on a separate host to have workload isolation

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  12. Automatic information when shared cluster is throttled

    When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.

    Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.

    6 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  13. typical query on collection report

    From the collections tab, show an aggregation of typical queries (for that collection) to help discover index opportunities

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  14. High resolution monitoring and alerting for WT dirty cache ratio, eviction workloads and checkpoints.

    Implement better monitoring and alerting for WT dirty cache ratio. This should include sub-minute resolution and support an understanding of eviction workload as well as performance impact of checkpoints under heavy write workloads.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow log level to be configured per cluster/node

    Atlas clusters don't support the setParameter command and, as a result, users aren't able to configure log levels. I understand the reasoning behind not exposing permissions to run setParameter to DB users so, in lieu of that, it would really helpful if Atlas users were able to configure log levels through the Atlas UI, preferably at the Node or Cluster level.

    Thanks!

    11 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  16. Provide offending query shape in Query Targeting alert notifications

    It would be ideal if the alert notifications for Query Targeting ratio alerts included a reference to the query shape that caused the alert to fire. This would assist customers in locating the exact query/queries with poor targeting ratios so that they can be optimized in a more expeditious manner.

    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

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add Elastic integration to Atlas

    Add support to send cluster metrics to Elastic. Elastic has recently been putting a lot of work into their APM and logging solution, this is now a viable alternative to NewRelic and Datadog and is gaining traction. It would be great if Atlas supported sending metrics to Elastic. Please see below for references

    https://www.elastic.co/apm
    https://www.elastic.co/siem

    The use case for this is the same as NewRelic or Datadog. I wish to monitor my Atlas clusters from inside Elastic, create dashboards and set up alerting

    17 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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  19. Monitoring Integration with Azure Event Grid

    Monitoring Integration with Azure Event Grid.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  20. Database Access History: sort and export

    Would be nice to export the database access history and/or sort by a column.

    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

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base