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

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.

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

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.

Currently there's no way to customize the subject line of either a system or global alert. The subject line only has the project name & time. It doesn't even say why the alert was generated until the email alert is opened. Having the ability to modify the subject line, even if it's to certain predefined fields such as alert condition for example would be helpful in addressing alerts in an efficient and effective manner.

Restrict the user depending on the type of project: dev, prod, etc to select a specific set of MongoDB Server versions that can be deployed.

Prior to 4.2 this was accomplished with version manager.

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.

it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.

What is the problem that needs to be solved? Allow to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps.

Why is it a problem? (the pain) As of now (2020-03-24) there's no way to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps (snmp.community controls both, Heartbeat and Alert Traps sent from Ops Manager's Application Server), some SNMP Monitoring Teams require different SNMP v2C communities for different set of SNMP v2C Traps (to separate Heartbeat Traps and Alert Traps).

As part of the Programmatic API Keys introduced in MongoDB Ops Manager 4.2, it would be good to have the IPs listed in the Host Mappings of a Project Deployment to be added as default whitelisted IPs when setting up a Programmatic API Key for same Project.

Need to be able to retain 1 day backups only or just daily backups. Need to reduce 3 day worth of archive.

The LDAP Query user's password appears in plain text in mongod.config file. The ability to mask its password in automation config file using credentialstool would mitigate a security risk.

Ability to enter multiple values for "KMIP Server Host" under KMIP Server Configuration in the Backup Configuration page of the Ops Manager Config. This would be similar to entering multiple values for 'kmipServerName' for deployments. This would help in terms of HA for KMIP; use a secondary KMIP server if the primary were to be unavailable.

alert when one or more monitoring agents in a project fail (not only when there are no agents left)

When utilizing the Filesystem Store, often files do not change between snapshots. In order to significantly save on space, the Backup Daemon could create hardlinks for the files in subsequent snapshots instead of extra copies of the file.

On Ops Manager up to 4.4.1 the Admin -> Organizations page shows only 100 organizations and there is no support for paginating the results.

Please improve the page by allowing the user to see more than 100 organizations.

Currently, MongoDB doesn't provide any way to enforce password policies. If there is some way for Ops Manager to enforce a configurable password complexity and age for user accounts managed through Ops Manager, that would be huge win. This can be as simple as adding UI-level validations to the create/edit user form.