Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Collect hardware metrics even if there's no managed mongo process

    Collect hardware metrics even if there's no managed mongo process

    Have Automation Agent collect hardware metrics on unmanaged mongo hosts.

    Automation agents doesn't collect hardware metrics unless there's a managed mongo process. This means we can't provide centralized system monitoring for a heterogeneous environment, where some clusters are running on their own and others are under automation, or on any non-managed host.

    7 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 / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  2. MMS Alert for Balancer Down status

    please provide an option in Ops Manager to monitor the balancer status and add to alerts?
    So, we will know if balancer is not running.

    Note:
    Normally the balancer would be disabled during backups and during a scheduled Balancing Window downtime.
    I believe that the Balancer has a duty cycle of either 10 secs when nothing recently to balance, or 1 sec when there's a bunch of balancing to do.
    Any alert would need to account for these:
    the changelog shows chunk moves commanded
    the actionlog shows balancer state change history
    the settings collection has the balancer state

    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

    1 comment  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow to configure `maxTimeMS` for commands executed from Ops Manager's Data Explorer

    What is the problem that needs to be solved? Allow to configure maxTimeMS for MongoDB commands which are executed from Ops Manager's Data Explorer.

    Why is it a problem? (the pain) A) Ops Manager's Data Explorer cannot work with views in case if the view is taking >15000 ms to be load. Data Explorer cannot work with find operations in case if that find operation is taking >15000 ms to be completed.

    5 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 / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  4. List shards in Deployment > Metrics' shard list in alphabetical order

    List shards in Deployment > Metrics' shard list in alphabetical order in Cloud Manager UI.

    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 / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add `serverStatus.uptime` counter info into Metrics

    What is the problem that needs to be solved? We already collect serverStatus.uptime counter info from each and every MongoDB Server process, so we just need to add serverStatus.uptime counter info into Metrics so that it will be possible to track serverStatus.uptime changes through the time.

    Why is it a problem? (the pain) If you'd like to calculate MongoDB Server process availability to know for how long your MongoDB Server process(es) was/were up and running, you'll need to analyze MongoDB Server process logs (in case if they are ever available for required period of time) to see last time MongoDB…

    7 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 / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base