Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Clear default values for New Replica Set and Cluster Component names in UI

    Clear default values for New Replica Set and Cluster Component names in UI

    Replica Set and Cluster Component names cannot be changed after deployment.
    The names are often overlooked while deploying and the defaults accepted configuring the names.
    If the fields were blank but mandatory (maybe with examples below the field) customers would be forced to choose logical names for their deployments.

    | Field | Current Default Value|
    | - | - |
    |Replica Set Id | myReplicaSet |
    | - | - |
    |Cluster Name | myCluster |
    |Shard Name Prefix | myShard |
    |Config Server Replica Set Name…

    1 vote
    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 →
  2. There is currently no way to use the UI to search a given hostname at a Global Level within an Ops Manager deployment.

    Please provide a feature in OM so we can search globally a given HOSTNAME to know about its related Organization/Replica Set

    1 vote
    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 →
  3. Ability to define a custom CA PEM file for Webhook configuration on Ops Manager

    Currently, Ops Manager user may require to add the CA for the TLS enabled Webhook Endpoint directly to the Java Trust Store. Adding CA to Java Trust Store also requires to re-apply if Ops Manager Application is upgraded or re-install.

    It would be best to have a feature in Ops Manager so that the user is able to upload the required CA via UI.

    1 vote
    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. Request Logs - Add timeframe to list of options

    While diagnosing historical issues "Request Logs" does not allow for selectable timeframes. As such, for these issues, logs must be manually gathered. Adding an optional timeframe will assist in diagnosing issues much faster.

    1 vote
    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 →
  5. Allow scheduling grooms

    Add the ability to schedule groom jobs at a specific point in time. Also expose this functionality through the API for easy modifications through configuration management tools.

    1 vote
    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. Add Alert for Projects which are not in Goal State

    Add an Alert type that is triggered if a project has not reached the goal state for certain amount of time.

    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 →
  7. Data Size on the header of Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages

    Data Size on the header of Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages appears to be incorrect.

    Reasearch indicates that the "Data Size" next to "Status" on the Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages possibly does not include "local" DB and may have an incorrect divisor.
    It also shows the same possibly incorrect value on each Deployment in the "Processes" page.

    We, DBAs, and our application teams, who have access to the Ops Manager, have been relying on this metric info each time we needed to find the size of a user DB.

    1 vote
    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. Ops Manager Base URL should support custom paths/sub-directories

    It may be desired to place Ops Manager behind a proxy or load balancer based on a URL path (aka sub-directory or prefix). For example, an nginx location may want to proxy pass connections to Ops Manager on "location /opsmanager"
    Currently, the Ops Manager Base URL appears to only accept and use the scheme, hostname/domain, and port. Additional path details are ignored by redirects sourcing from javascript functions and html links/resources.

    Current workarounds require a unique/dedicated server name for proxying or load balancing to Ops Manager web service(s).

    This feature request is for supporting custom URL paths when using Ops…

    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 →
  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. Configure Ops Manager LDAP Auth via an API call

    Currently, there is no way to enable LDAP Auth for the Ops Manager Users via an API call.

    This essentially means that one would not be able to use LDAP and ci/cd simultaneously with Ops Manager.

    Mongodb enterprise support has confirmed that in the event of disaster recovery or a deployment of a new cluster, manual steps must be done to enable LDAP during a ci/cd deployment.

    It should not be expected to sign in and manually do anything in a web gui in an enterprise solution. It is simply not scalable.

    1 vote
    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. 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 →
  12. Ops Manager Prometheus metrics

    MongoDB Ops Manager would need to expose endpoints for Prometheus for MongoDB Clusters. There are a number of metrics that popular MongoDB Exporters do not provide, for example:
    1. Enterprise Backup status
    2. Replication Alarms
    3. Agent statuses
    4. A number of Cluster statuses
    etc

    There is no way to get this data into Prometheus at the moment

    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 →
  13. Ability to send SNMPv3 Alert Traps for configured Ops Manager Alerts

    What is the problem that needs to be solved? Ops Manager Alerts should have possibility to send SNMPv3 Alert Traps to configured destinations. SNMPv3 provides better authentication, data encryption and message integrity in comparison to SNMPv2c protocol.

    Why is it a problem? (the pain) It is mandatory to use SNMPv3 in many enterprise deployments as SNMPv2c does plaintext community string authentication without encryption (SNMPv3 does MD5/SHA1 hashing for passwords and provides encryption for SNMP data).

    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 →
  14. Add 4.4 tool to PATH

    Since MongoDB 4.4 the tools are located in another folder that is not included in the automation agent bash profile:

    [root@n1 mongodb-mms-automation]# cat /etc/profile.d/mongodb-mms-automation-agent.sh
    export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}

    Would be nice to have also the mongo tools in the path

    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 →
  15. Improve backup job status in Backup jobs summary table

    When checking the backup job details for a 4.2 deployment, this is always reporting to be performing a "WT Checkpoint" even though it is not exactly generating a snapshot at that point in time.

    The request is to enhance the reporting for this summary table in order to get further details on what the Backup Module is doing at that precise point in time. If it is awaiting for the instruction to execute a snapshot, in the process of transferring blocks, etc.

    5 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 →
  16. Use word, not letter to define log levels in Ops Manager

    The following log messages are "info" level messages which can be found in the kubernetes logs from the ops-manager-db pods:

    ```sh
    {"logType":"mongodb","contents":"2020-12-16T02:42:28.557+0000 I WRITE [conn7329] update monitoringstatus.config.agentSessions command: { q: { id: "mongodb-rs-1.mongodb-rs-svc.mongodb.svc.cluster.local-48cc126fc451d9fa2ffa7569363971f2-5fbedc8dc354771c77dd1932", s: "KHNA9JiqXcos5V0d" }, u: { $set: { s: "PRIMARY", p: true } }, multi: false, upsert: false } planSummary: IXSCAN { id: 1 } numYields:0 queryHash:6C451E2F planCacheKey:38AD5486 ok:0 errMsg:"E11000 duplicate key error collection: monitoringstatus.config.agentSessions index: cid1s_1 dup key: { cid: ObjectId('5fbedc8dc354771c77dd1932'), s: \"PRIMARY\" }" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: {…

    1 vote
    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. Rewrite Informational Message "E11000 duplicate key error collection"

    Rewrite the informational AppDB log message so that monitoring tools such as Dynatrace and Splunk does not consider this message as an error message.

    1 vote
    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. Update automation config through API without pushing entire config file

    For updating any Automation managed parameter, the only method through API is involving pushing the entire Automation config (which is a json file of hundreds lines) with modifications/addition all together.

    Even though I just want to update one single value.

    Is it a bit dangerous that there may be human mistake when modifying such a large json file. Wrong configuration may be push to the server.

    Graceful if there is a feature which allow user to partial update the configuration through API.

    Ref Case: 00730243

    1 vote
    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. Add ability to merge metrics when host renamed

    If a host is renamed and a new mapping is made with a unique ID, there is no way to merge the metrics to view the, historically.

    Adding the ability to merge metrics from previous hosts (when the user is sure the hosts are equivalent) would allow history to be viewed and maintained.

    1 vote
    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