Skip to content

Ops Tools

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

37 results found

  1. integration with Mattermost for notifications

    It would be good to replicate the integration with Slack but using Mattermost. Mattermost is open source and allows the companies to deploy their own messaging server. Some organizations are moving from Slack to Mattermost for this reason.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The Get Host, Process, System Measurements Ops Manager API doesn't exactly provides hostInfo.system.memLimitMB.

    Add to The Get Host, Process, System Measurements Ops Manager API the hostInfo.system.memLimitMB.
    Or add an API to get the pings value.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ability to sort by shard_name in project metrics

    We should have a button to sort by shard_name on top

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. disable auth on metrics

    Opentelemtry-Collector does not support secrets for ServiceMonitor/PodMonitor resources, which generates authorization issues while trying to scrape the metrics endpoint of MongoDB.

    I'm looking for a way to disable the basic_auth on the metrics endpoint of MongoDB, I already tried a lot of ways, including an empty username/password, but nothing worked, any help would be highly appreciated.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. mongod startupWarnings

    Create an "alert" to send notificactions when a mongod proccess has, for any reason, startup warnings.

    e.g.
    1)
    The configured WiredTiger cache size is more than 80% of available RAM. See http://dochub.mongodb.org/core/faq-memory-diagnostics-wt

    2)
    /sys/kernel/mm/transparent_hugepage/defrag is 'always'.

    3) Others.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Replica Set size Alert

    Have an Alert in Ops Manager to notify that a Replica Set is approaching the maximum recommended size (ie: 2TB) and that it should be converted into a Sharded Cluster.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow drag-and-drop of metric graphs from different replica set members

    Our use case is we have a replica set, but the east nodes and west nodes are on disk mounts with different names, so they won't appear on the same line in the Metrics tab. We should be able to drag and drop on a replica set member level, not just the metrics level. This allows more customization of metric graph layout.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Providing a grafana dashboard for an on-premise cluster

    It would be interesting to provide a grafana dashboard when integrating with prometheus.

    The documentation is indeed very limited concerning metrics when you're on a mongoDB on premise cluster.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Send Alerts When Network Access is Updated

    Create an alert when IP Addresses are added or removed from a cluster network access whitelist.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add "Cluster Tier" and Provisioned "IOPS" as options in MongoDB Metrics Charts in Atlas

    If these charts were available, it would enable to the user to visualize the Tier and IOPS of the cluster during specific time ranges, and compare to other metrics such as CPU, iowait, etc.

    In my team's experience, we use Atlas auto-scaling to allow a cluster to scale up/down based on load, but when looking at Metrics it is not clear which Tier the cluster was in (e.g. "M30") when evaluating other metrics like CPU utilization. We are able to manually track Cluster Tier by viewing the Project Activity Feed, but if this data was integrated into Metrics it would…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Do not trigger spurious COLLSCAN alerts for getmore commands during watch

    Here's what MongoDB support summarizes about the current behavior: "Upon consulting with the team, they have confirmed that sometimes change streams can trigger collection scans, but these alerts are an artifact of how we calculate the metric today. Unfortunately at the moment, there is no fix for these alerts"

    My suggestion is to fix how the metric is calculated. What is happening in the getmore is not a real COLLSCAN, and it should not be reported (and alerted) as such.

    (Bonus points for including context information in the COLLSCAN threshold alert showing the collection and operation. Just knowing there has…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Export Reports and Graphs

    OPtions to export the reports and graphs into a PDF or office tool will help Incident Management process to a great extend.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Include "Fetch Time" in Profiler timings

    When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

    In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

    Is there a way to configure Profiler to be more realistic,…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. connection

    Ops Manager only shows number of connection. Most DB monitoring tool shows where the connection is coming from and whats being run from the session. This needs to be a part of Ops Manager

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Update MongoDB driver in Elastic metricbeat and validate operability with Atlas

    The metricbeat data collection agent from Elastic currently has a MongoDB module for capturing low level metrics from a MongoDB instance. It's using a very old MongoDB driver that doesn't work with recent versions, nor work with Atlas.

    I realize metricbeat isn't a MongoDB product or supported integration but it seems like it'd be low effort from an experienced Golang developer (which I am not) and remove an impediment from potential requirements around MongoDB metrics having to be captured using company-standard observability solutions. Thanks!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. disk iops

    Can you please revert the change to metrics view for disk iops? It it completely unreadable and meaningless now.

    There used to be 2 lines that made sense. Now there are 4... but looks like a bar chart. Anyway. Can't read it.

    I would suggest.
    1. have 1 view with 3 lines: 1 for the average read and 1 average write and 1 average BOTH.

    1. have a second view showing the "burst" performance. Draw this as a LINE or scatter plot. Whatever you are drawing now is inscrutable.

    thanks!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add a free user field in alert configuration

    We'd like to be able to link some free text data with an alert configuration.

    One use case: we forward open Ops Manager alerts to other monitoring systems of our company (using the API). Those monitoring systems need some specific data that should be associated with the forwarded alert.

    Another use case: we have a Python script/lib that provision alerts in several projects.
    Having a free field could be used to link source code definition with the published alert in Ops Manager and make a cleaner publishing script (currently it consists in delete all / publish all alerts which is…

    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

    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