Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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 →
  2. 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 →
  3. 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. 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 →
  5. Ability to configure all destinations for SNMPv2c Alert Traps in a single place

    What is the problem that needs to be solved? Ops Manager needs to have ability to configure all destinations for SNMPv2c Alert Traps in a single place (so that single place needs to be updated instead of dozens of individual Ops Manager Alerts).

    Why is it a problem? (the pain) In case if there's a change in SNMPv2c Alert Trap destination(s), it becomes effort to change the respective hosts for each of the alert. This process requires some time (unless customer script it via Ops Manager's API) if amount of configured Ops Manager Alerts is high, and the process itself…

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. Create AppDB user with backup role to allow execution of mongodump

    For the purpose of regularly performing backups of the AppDB using mongodump --oplog.

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. Add configuration option for MongoDB Agent (Automation Module) to compress its logs (same as Monitoring/Backup Modules)

    What is the problem that needs to be solved? MongoDB Agent (Automation Module) doesn't have ability to configure Automation logs compression.

    Why is it a problem? (the pain) Current behavior of MongoDB Agent (Automation Module) to not allow to compress its logs is sub-optimal since MongoDB Agent (Automation Module) logs takes more disk space if its logs are kept uncompressed.

    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  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  10. Send `Monitoring is down` and `Backup is down` alerts for each MongoDB Agent (Monitoring/Backup Module) and include hostname information in

    What is the problem that needs to be solved? Monitoring is down and Backup is down alerts needs to be sent for each individual MongoDB Agent (Monitoring/Backup Module) which become down, Monitoring is down and Backup is down alerts should include hostname information in them.

    Why is it a problem? (the pain) Customer can't easily identify which MongoDB Agent (Monitoring/Backup Module) become down without hostname information available in the alert (in multi-project environment this becomes operational pain for the customer).

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make it possible to prevent incessant Automation log messages about unexpected field in process memory metrics map

    My automation manager posts an info message about unexpected fields in process memory metrics map every minute. It's polluting my logs. I would like a way to fix the underlying problem or, if it cannot be fixed, then don't tell me about it in the logs.

    Here are some examples:
    mongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: thp_enabled. Skipping

    mongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: speculationstorebypass. Skipping

    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  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. Install Managed MongoDB Processes as Services in Linux

    In Windows, managed MongoDB processes are installed as services. In Linux, they are not. It would be great if managed processes were installed as services so that system administrators would have better control over startup and shutdown behavior, among other things.

    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  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ops Manager

    In Ops Manager ,Whenever we do changes in the configuration the deployed mongodb instnaces ,GUI prompt for Review & Deploy ,If we have a provision for schduling the deployment in later time would fullfil the real Automation.


    • Do the changes at convenient time

    • Do deploy thru a schedulers

    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  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. Filter/Sort Process List View

    In previous versions of Ops Manager, you could filter the process list page. It would be nice to bring that back, so we could quickly identify processes which do not have recent pings, etc.

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  17. arm64 support for Cloud Manager Agent

    We would like to install Cloud Manager Agent on arm64 based linux machines.

    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  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  Admin →
  18. Start MongoDB Agent service (`mongodb-mms-automation-agent.service`) automatically after OS restart, make it default behavior

    What is the problem that needs to be solved? MongoDB Agent service (mongodb-mms-automation-agent.service) does not start (by default (disabled; vendor preset: disabled)) automatically after OS reboot.

    Why is it a problem? (the pain) OS restarts can be frequent, and current default behavior (disabled; vendor preset: disabled) of MongoDB Agent not to start after OS restart causing additional downtime for customers.

    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  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enable Ops Manager alerts on any FATAL or ERROR lines in the mongod/mongos logs

    What is the problem that needs to be solved?

    All possible error states and failures reported in the mongod and mongos log files are not raised as alerts in the Ops Manager alerting system. This prevents users from configuring alerts on important events in MongoDB deployments.

    Why is it a problem? (the pain)

    For some users specific errors such as FATAL or ERROR lines in the mongod log need to be alerted and addressed with urgency. Since the specific high priority event is different for different users, a configurable, string matching (regex) driven alerting system that constantly monitors the mongod

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
  • Don't see your idea?

Feedback and Knowledge Base