Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Plugin for Moogsoft monitoring tools.

    Currently, Ops Manager does not have the plugin for Moogsoft monitoring tools, it would be great to add the feature to the future release of Ops Manager.

    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. Grant permission to access Real Time tab to Project Read Only users

    Accessing the Real Time metrics tab requires at least the Project Monitoring Admin role but this role has other privileges to administer alerts and manage hosts as well.

    It is more appropriate to enable the read-only access user (Project Read Only role) to access the Real Time metrics tab.

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. Create localhost exception for POST /unauth/users API call

    The purpose of this request is for Ops Manager to implement a "localhost exception" for the API call POST /unauth/users so it can only be executed under two conditions:
    1. No other users exists in the setup.
    1. Ops Manager runs in "invitation only" mode.
    1. Ops Manager has not been configured for LDAP.
    1. The API call can only originate from an IP or alias that belongs to one of the Ops Manager Application server.

    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. ability to re-order alerts

    when you add new alert there is no way in GUI to order/reorder them. It's hard to maintain large set of alerts.

    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 configuring Ops Manager to bypass Proxy for the S3 on-prem

    Allow configuring Ops Manager to bypass Proxy for the S3 on-prem.

    Configuring the S3 Blockstore also respects the Ops Manager Proxy settings. This is not practical if it is the S3 on-prem which typically does not require external (Internet) access.

    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  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  6. Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots

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

    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 →
  7. MongoDB Agent alters the root $PATH variable

    The MongoDB Agent installation via RPM adds the /var/lib/mongodb-mms-automation/bin to root's $PATH by placing the mongodb-mms-automation-agent.sh script under the /etc/profile.d:
    $ pwd
    /etc/profile.d
    $ sudo cat mongodb-mms-automation-agent.sh
    export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}

    This breaks my customers security standards.

    Moving the script does not appear to affect the functionality of the MongoDB Agent and updating the agent via the OM UI does not add back the script.

    We would like the ability to either select the contents of the MongoDB Agent rpm or be asked during the rpm installation whether or not to install the mongodb-mms-automation-agent.sh script.

    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. Allow configuring custom builds at the organisation or global level (Admin panel)

    It must be done at the project level at the moment, generating an operational costs for those environments with a large number of projects.

    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 →
  9. Implement IAM role authentication for AWS SES in Ops Manager

    At the moment using AWS SES for email delivery in Ops Manager requires AWS Access Key and Secret Key. Please implement the IAM role authentication for this option as it has been done for the S3 endpoints.

    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 →
  10. 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.

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  11. OpsManager Pod should not have credentials in environment variables but store and retrieve from a k8s secret

    OpsManager database password is exposed as environment variable.

    OMPROPmongo_mongoUri holds credentials of the OpsManager Database.

    OpsManager Pod should not have credentials in environment variables but store and retrieve from a k8s secret.

    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  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  12. adminCredentials secret should always be source of truth for OpsManager

    The secret is only taken into account by OpsManager initially when OpsManager is deployed. As soon as the password of this user is changed in OpsManager, this secret is out of sync.

    From the docs: "Use these credentials to log in to Ops Manager for the first time. Once Ops Manager is deployed, you should change the password or remove this secret."
    https://docs.mongodb.com/kubernetes-operator/v1.4/tutorial/plan-om-resource/#prerequisites

    Option 1: This secret should be in-sync with the OpsManager database. Preferably the sync should be from the k8s secret to the OpsManager database.

    Option 2: Create a CRD "MongoDBOpsManagerUser" that handles User/Password management for OpsManager similar…

    1 vote
    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 →
  13. Provide a Kubernetes native way to deploy a MongoDB instance without any interaction towards the OpsManager API

    When deploying a MongoDB resource to a newly installed Operator and OpsManager the user has to

    Create an Organization, API keys and IP whitelisting in OpsManager
    Create a Secret and ConfigMap with the data returned from OpsManager
    Specify this Configmap as "configMapRef" in the MongoDB resource.

    Please provide a k8s native way to deploy a MongoDB instance without any interaction towards the OpsManager API. The MongoDB Operator should create the Organization, API keys and IP whitelisting in OpsManager and create the secret and configmap.

    Option 1: Create a CRD "MongoDBOpsManagerOrganization" that has a reference to a secret (containing the private…

    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  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  14. Periodically notify users of unused versions located in versions directory

    As a safety measure for admins in Ops Manager to avoid facing issues due to unnecessary disk occupation under the Ops Manager installation directory:

    Send periodic notifications (configurable) i.e: once a month; to notify what binaries are not being used by none of the components in their environment so they can evaluate to delete them in order to free up space on their Ops Manager servers.

    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 →
  15. Prevent users from importing a replica set or shard with the same name as other pre-existing replica sets/shards

    When a user imports a cluster into a project with the same name, it causes issues like breaking backups of pre-existing clusters.

    Checking the replica set name against the names of other replica set names will prevent having to terminate backups and remove and re-import clusters, starting over.

    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  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to sort by shard_name in project metrics

    We should have a button to sort by shard_name on top

    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  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  17. Atlas Open Service Broker - Roles

    Is it possible to add the support for user roles to the bind api for the Atlas Open Service Broker?

    Customers that are currently using the OSB are limited in that they are having to separately manage the creation and assignment of roles.

    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  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Ops Mgr "Insufficient oplog size" is confusing and prevents backups

    When using Ops Manager UI (I've not checked the API) to declare a MongoDB cluster to be backed up, Ops Manager tries to be a good citizen and check to see if the clusters oplogs are large enough, based on their recent usage to hold at least 3 hours worth of data based on the last 24 hours of usage patterns. if the check fails, the user is prevented from enabling backup and is shown the warning:

    "Insufficient oplog size: The oplog window must be at least 3 hours over the last 24 hours for all members of 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

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow to configure options for automation agent logs

    Currently there is no way in Kubernetes operator to configure how long automation/backup/monitoring agent logs should be stored. they can easily occupy all space in pod.

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow honorSystemUmask to be set on Ops Manager HEADDBs

    If honorSystemUmask is set to false, new files created by MongoDB have permissions set to 600, which gives read and write permissions only to the owner. New directories have permissions set to 700.

    As a result it makes it difficult to read the HEADDB logs in some environments. Allowing honorSystemUmask to be configurable would allow the customer to choose permissions based on their own security policies.

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

Feedback and Knowledge Base