462 results found

1. Add a free user field in alert configuration

   We'd like to be able to link some free text data with an alert configuration.

   One use case: we forward open Ops Manager alerts to other monitoring systems of our company (using the API). Those monitoring systems need some specific data that should be associated with the forwarded alert.

   Another use case: we have a Python script/lib that provision alerts in several projects.
   Having a free field could be used to link source code definition with the published alert in Ops Manager and make a cleaner publishing script (currently it consists in delete all / publish all alerts which is not ideal).

   We'd like to be able to link some free text data with an alert configuration.

   One use case: we forward open Ops Manager alerts to other monitoring systems of our company (using the API). Those monitoring systems need some specific data that should be associated with the forwarded alert.

   Another use case: we have a Python script/lib that provision alerts in several projects.
   Having a free field could be used to link source code definition with the published alert in Ops Manager and make a cleaner publishing script (currently it consists in delete all / publish all alerts which is… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Monitoring / Alerts  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Assignment labels in YAML for Snapshot storage

   Currently, if you want to assign a snapshot store to a certain project, it is required to access the Admin view and configure the "Assignment Labels" property under Backup > Snapshot Storage with the name of the corresponding project.

   AFAIK, it is not possible to assign this configuration in the Ops Manager's YAML. E.g.:

   s3Stores:
   - mongodbResourceRef:
       name: s3-metadata-db
     mongodbUserRef:
       name: s3-meta-store-user
     name: s3store1
     pathStyleAccessEnabled: false
     s3BucketEndpoint: endpoint1.corp
     s3BucketName: backup1-bucket
     s3SecretRef:
       name: s3-credentials
   - mongodbResourceRef:
       name: s3-metadata-db
     mongodbUserRef:
       name: s3-meta-store-user
     name: s3store2
     pathStyleAccessEnabled: false
     s3BucketEndpoint: backup2.corp
     s3BucketName: backup2-bucket
     s3SecretRef:
       name: second-credentials
   

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Enterprise Kubernetes Operator  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. GUI for Queryable Snapshots

   It would be good to have a GUI created for the queryable snapshot interface so less experienced users, that may not have any mongod experience, can successfully restore a collection/document without additional training.

   Ideally, the feature allows for the creation of some subset of documents using a query building tool (even collection level would be acceptable) that can then be pushed to a target environment automatically or pushed to a mongodump file that can be used as a restore tool later. Their primary concern is just to ensure that individuals without direct mongod experience or server access can generate a restore and circumvent the current process of spinning up a tunnel and creating a query manually.

   An example workflow would be:

   1. Deployment -> Backups -> Enable Queryable Restore for Source Job for PIT
   2. Click Query Snapshot Builder
   3. Select collection or build query
   4. Display example result set
   5. Select push to dump or push to cluster a. Push to snapshot: generate mongodump for query/collection and provide example mongorestore string b. Push to cluster: select target cluster and confirm deploy

   It would be good to have a GUI created for the queryable snapshot interface so less experienced users, that may not have any mongod experience, can successfully restore a collection/document without additional training.

   Ideally, the feature allows for the creation of some subset of documents using a query building tool (even collection level would be acceptable) that can then be pushed to a target environment automatically or pushed to a mongodump file that can be used as a restore tool later. Their primary concern is just to ensure that individuals without direct mongod experience or server access can generate a… more

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Apply Project Maintenance Windows to Global Alerts

   Apply Project Maintenance Windows to Global Alerts

   Make the existing Project-level maintenance windows also silence Global alerts associated with the Project.

   We have many projects that share the Global Alerts and do not want to turn off all global alerts as we still need that alerting for the projects that are not being worked on.

   In combination with the existing API for Project Maintenance Windows, this really allows full control.

   14 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Memory metrics summed for Project/Organization

   Memory metrics summed for Project/Organization
   Request UI ability to sum total memory used by mongo processes per Project and Organization.
   The UI does provide Process/Replca Set/Cluster Memory Statistics.
   Metrics are available per instance but there is currently no non-programatic way to get the SUM of all used memory for a given Project nor Organization.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Managing mongoDB containers having multiple DNS names through automation agent

   We got mongoDB running on openshift pods across 2 separate openshift clusters and it runs perfectly fine but we are now facing issue with doing mongoDB restore, and that has led to us now wanting to use automation agent to control the mongod process on the containers.

   The major challenge we are facing is that we run into issues when automation agent runs rs.initiate() and as part of the process tries to gather the hostname of the pod by running hostname -f command. The trouble is we have to deal with separate openshift clusters and have got mongod replica set members split across separate openshift clusters so we use a global DNS name so that the hostnames are resolved at the DNS level and allows for communication to flow through across seperate openshift clusters.

   We want to have a feature which would allow us to choose what hostnames the automation agent should use in order to create the replica set. We also feel, this would be a huge asset for anyone trying to control the mongod containers from the ops manager and would give mongoDB an edge when it comes to running databases on containers.

   We are also happy to provide any assistance in this regard and want this feature to be considered on a high priority as it is a BLOCKER for us.

   We got mongoDB running on openshift pods across 2 separate openshift clusters and it runs perfectly fine but we are now facing issue with doing mongoDB restore, and that has led to us now wanting to use automation agent to control the mongod process on the containers.

   The major challenge we are facing is that we run into issues when automation agent runs rs.initiate() and as part of the process tries to gather the hostname of the pod by running hostname -f command. The trouble is we have to deal with separate openshift clusters and have got mongod replica set… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. enable x509 security command

   mongocli ops-manager security enable [MONGODB-CR|SCRAM-SHA-256]

   add an option for x509

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Automated restores between multiple Ops Manager deployments

   Ability to utilize API and/or UI to restore a snapshot downloaded from one Ops Manager deployment to a separate distinct Ops Manager deployment.

   Some environments require separation of Production and Staging systems, including Ops Manager deployments. It is desirable to use Production data in some testing scenarios. Currently the data has to be loaded or restore manually.

   21 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Attain granularity on the Ops manager backups & restore

   Backups:Under a project, in a single cluster we may deploy multiple databases which belongs to different applications that are somehow interlinked in terms of their functionality. Different databases requires different backup strategies, retention periods, and so different snapshot schedules. However, the level of granularity on Ops Manager "Continuous Backup" doesn't match the above requirement.

   Restore: How could we restore a single collection, or a database without touching the other databases/collections within a cluster? The restore process that we have today seems to be restoring the whole cluster and not to the level of database/collection. Queryable backup snapshot seems to be a way to attain this, however an alternative to avoid major setup changes and speed up the restore process incase of any emergency events.

   It would be great if this can be added as product enhancement in future releases.

   Backups:Under a project, in a single cluster we may deploy multiple databases which belongs to different applications that are somehow interlinked in terms of their functionality. Different databases requires different backup strategies, retention periods, and so different snapshot schedules. However, the level of granularity on Ops Manager "Continuous Backup" doesn't match the above requirement.

   Restore: How could we restore a single collection, or a database without touching the other databases/collections within a cluster? The restore process that we have today seems to be restoring the whole cluster and not to the level of database/collection. Queryable backup snapshot seems to be… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Create AppDB user with backup role to allow execution of mongodump

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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 is prone to human errors (typos, etc.).

    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… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. 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.

    •  

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Ability to control Ops Manager log rotation from an Admin Page in the UI

    The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

    Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

    Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

    Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses to configure Ops Manager logs and log rotation for /opt/mongodb/mms/logs/mms0.log and /opt/mongodb/mms/logs/daemon.log. By default this is configured with the following settings:

    
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${log_path}.log</file>
<encoder class="com.xgen.svc.mms.util.HeaderPatternLayoutEncoder$Classic">
<pattern>
%d{"yyyy-MM-dd'T'HH:mm:ss.SSSZ"} [%thread] %XF{groupId, "gid:%s "}%XF{jobId, "jobId:%s "}%-5level %logger [%file.%method:%line] - %msg%n
</pattern>
</encoder>
<!-- Rollover the logs once per day, keep 30 days, compressed -->
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${log_path}.%d{yyyyMMdd}.log.gz</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
</appender>


    The file /opt/mongodb/mms/conf/logback-access.xml controls rotation of the /opt/mongodb/mms/logs/mms0-access.log. It has the same <!-- Rollover the logs once per day, keep 30 days, compressed --> policy.

    The logs will be compressed and rotated each day and deleted after 30 rolling days. If you modify the maxHistory option to 10, this should delete the files after 10 days. Please note that any upgrade of Ops Manager may overwrite this change with a new configuration file. Additionally, after modifying these values you will need to restart Ops Manager.

    The /opt/mongodb/mms/logs/mms-migration.log, mms0-startup.log and daemon-startup.log log files are not rotated as it contains only some log entries generated during the startup/migration phases of the Ops Manager Application Server processes.

    The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

    Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

    Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

    Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. mms.ldap.bindPassword

    We need to deploy ops manager with LDAP settings via yaml file where one of the setting "mms.ldap.bindPassword=" requires clear text password.
    Is there any secure option to this?

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. 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

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Operator automatically provision an Ops Manager programmatic API key

    Operator automatically provision an Ops Manager programmatic API key, The current instructions require human intervention to create an AP

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Changes to Backup Configuration

    Ability for changes in a project's Backup Configuration page to take effect without having to terminate and restart backups. Terminating backups removes all existing backups thus exposing an organization to risk. Backups can be stopped and restarted for the changes to take effect but not completely terminate them. This would help when changes are needed into terms of backup daemons, blockstores, types of blockstores, etc.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Notify about SSL/TLS Certificate Expiration Date & Time to warn customers about potential impact on their deployment availability

    What is the problem that needs to be solved? Customers run into SSL/TLS Certificate Expiration issues (where SSL/TLS certificate has expired) on their Ops Manager and MongoDB Server environments and they do not get any early notifications from Ops Manager about SSL/TLS Certificate Expiration.

    Why is it a problem? (the pain) Customers who use Ops Manager to manage/monitor their MongoDB Server deployments are running into situation where their configured SSL/TLS Certificates are expired, and thus have potential downtime for their applications.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close