Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add hostname/port attributes into all Cluster/Replica Set alert types

    What is the problem that needs to be solved? Add hostname/port attributes into all Cluster/Replica Set alert types generated via SNMP Alert Traps, Ops Manager's Public API calls (Project/Global Alerts) and Alert Webhooks (Project/Global Alerts).

    Why is it a problem? (the pain) Hostname/port attributes are currently missed in Cluster/Replica Set alert types and we only provide a name of the Cluster/Replica Set for which the alert was generated. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see hostname/port information of a Shard/Replica Set for which such alert was generated, in order to quickly understand…

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  2. Possibility to send an alert over all/selected alert channels, if all/selected alerts can't be delivered

    What is the problem that needs to be solved? Send an alert over all/selected alert channels, if all/selected alerts can't be delivered by Ops Manager's Application Server.

    Why is it a problem? (the pain) We can miss an alert (or multiple alerts) from Ops Manager's Application Server if configured alert channel become unavailable since all Ops Manager Alerts are working in fire-and-forget style without any checks/mechanisms to see if the alert was delivered (some alert types can't have that guarantee at all (e.g. SNMP Alert Traps)).

    Ops Manager - Alerting Framework.png flow diagram has been attached to this Feature Request…

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add support for collections with default locale

    At present if a collection has a default collation configured, sharding such a namespace via Ops Manager results in a failure with the following symptom:

    <myCluster_mongos_131> [13:21:17.050] Plan execution failed on step ShardCollections as part of move ShardCollections : <myCluster_mongos_131> [13:21:17.050] Failed to apply action. Result = <nil> : <myCluster_mongos_131> [13:21:17.050] Error calling shardCollection on sh.myColl with key = [[a 1]] : <myCluster_mongos_131> [13:21:14.994] Error executing WithClientFor() for cp=mubuntu:27017 (local=false) connectMode=AutoConnect : <myCluster_mongos_131> [13:21:14.993] Error running command for runCommandWithTimeout(dbName=admin, cmd=[{shardCollection sh.myColl} {key [{a 1}]} {unique false}]) : result={} identityUsed=mms-automation@admin[[MONGODB-CR/SCRAM-SHA-1]][24] : (BadValue) Collection has default collation: collation: { locale: "fr", caseLevel:

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add Ops Manager's Org ID/Org Name/Project Name into Project/Global Alerts API calls & Alert Webhooks

    What is the problem that needs to be solved? Ops Manager's Org ID/Org Name/Project Name attributes needs to be added to Project (GET /groups/{PROJECT-ID}/alerts) / Global (GET /globalAlerts) Alerts API calls and Alert Webhooks.

    Why is it a problem? (the pain) Ops Manager's Org ID/Org Name/Project Name attributes are currently missed in Project (GET /groups/{PROJECT-ID}/alerts) / Global (GET /globalAlerts) Alerts API calls and Alert Webhooks. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see Ops Manager's Organization ID/Organization Name/Project Name in order to quickly understand to…

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add Global MongoDB Agent Upgrade ability

    Add the ability to upgrade all MongoDB Agents across all Projects at the same time instead of clicking on the banner for each Project.

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  6. Single Project Programmatic API Keys should not require Org User Admin role for IP Whitelists update

    When setting a Programmatic API Key in the MongoDB Ops Manager for a given Project, it seems Project Owners are unable after setting the Key to update the IP Whitelist as they require Organization User Admin role to perform such action (screenshot attached).

    I guess this makes sense if the same Programmatic API Key is shared between multiple Projects inside the same Organization, but not really if this is applied only to one single Project (i.e. Project Owners should be able to amend the IP Whitelisting of their own API Keys).

    I wonder if this could be enhanced in further…

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  7. 4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  8. Federate different Ops Manager instances

    When multiple Ops Managers are running across multiple environments it is difficult see the overall picture.
    A a federated dashboard that can provide a view into different environments, see overall list of clusters and some basic information about them.

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve backup process with automatic reparation of broken job

    Enhance the Ops Manager feature for the detecting of broken processes, validating its sanity, so that Ops Manager could "un-break" processes and start regular backups without any manual intervention.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  10. Include Replica Set Horizons in Connect to your Deployment Modal

    Clicking on the "Connect to this replica set" should open a modal that includes the Replica Set horizon host and port (if configured) in addition to the host's FQDN. This will help users determine their connection settings without requesting details from the kubernetes cluster administrators that deployed the database.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support __exec setting for the MongoDB deployment in Automation

    The deployment that utilizes __exec setting is unable to import to Automation as well as it is unable to deploy the deployment by Automation with this setting.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow customization of Alert's Subject/Body

    Currently alerts do not allow for any customization of the Subject or Body. It would be useful to allow customization of both the Subject and Body of emails and other alert methods. This would allow customers to add information, such as links to internal runbooks or documentation, to assist with resolving the alert.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  13. Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots

    Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  14. Make snapshot retention policy more customisable

    Make the retention policy of Ops Manager snapshots customisable so we can choose custom values (like 21) to be more flexible with the settings.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  15. index review before sharding with OPS Manager

    Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
    This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
    So, several features could exist :
    - before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
    -…

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  16. Do not download EOL releases

    Currently our Ops Mgrs keep re-downloading EOL releases of mongodb, e.g. mongodb-linux-x8664-2.6.12, mongodb-linux-x8664-3.0.15, etc. Ops Manager should automatically exclude EOL releases - they are taking up unnecessary disk space.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  17. Ops Manager API call for Host Mappings

    This feature request is for a new Group/Project API call for the management of the host mappings created in Ops Manager from monitoring information. Whether it be an endpoint for "Reset Duplicates" or full featured create/delete of individual host mappings, both will alleviate issues where overlapping mappings affect monitoring in Ops Manager.

    Note: The issue of overlapping mappings may occur when a mongod process has moved/changed IP addresses multiple times. With enough cycling (as seen in Kubernetes clusters with frequent pod restarts), eventually a previously mapped IP address may now be associated with a different mongod process.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  18. Repilca Set Election - Even Number of Nodes

    WE have a 4 node replica set and when we removed 2 of the nodes at one time the election process didn't know how to elect a new primary. We would like the election process to accommodate an even number of replica set nodes.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Disable the dropdown to add Agent functions on hosts that don't have the MongoDB Agent installed and were only imported for Backup/Monitori

    Disable the dropdown to add Agent functions on hosts that don't have the MongoDB Agent installed and were only imported for Backup/Monitoring.
    The elipsis (...) selections to add Monitoring & Backup Agent functions are available on hosts without the MongoDB Agent. If selected the function appears on the host as grey and standby. This is misleading. The options should not be available on hosts without the MongoDB Agent.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  20. Activate multiple monitoring module in appDB monitoring project

    On Servers Page, Activate/Deactivate Monitoring/Backup module should be activated. So that multiple monitoring module should be activated for hot stand by.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base