Add third-party service integration for Microsoft Teams, as we do for Slack.
Most likely the following can be leveraged to achieve the integration: https://docs.microsoft.com/en-us/graph/teams-proactive-messaging

If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1".
OPS Manager does not provide any details where it was triggered.
it would be nice to get db/collection/query which caused this issue. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group.

What is the problem that needs to be solved? SNMP traps for AUTOMATION_AGENT_DOWN, MONITORING_AGENT_DOWN, BACKUP_AGENT_DOWN alert types does not contain hostname information in .1.3.6.1.4.1.41138.1.1.1.4 (.iso.org.dod.internet.private.enterprises.mms.server.serverMIBObjects.mmsAlertObject.mmsAlertHostAndPort) OID.

Why is it a problem? (the pain) User is blocked to act quickly on the alert and identify the host where Ops Manager's Automation/Monitoring/Backup Agent is in DOWN state. Missing <HOSTNAME>:<PORT> information at .1.3.6.1.4.1.41138.1.1.1.4 SNMP OID does not allow user to map AUTOMATION_AGENT_DOWN, MONITORING_AGENT_DOWN, BACKUP_AGENT_DOWN alert types into a particular hostname.

In order to test snapshots automatically, create a new job type that allows the Backup Daemon to download the snapshot from the snapshot store, then run validate on each collection.

If any collection fails validation, send an alert to the Backup Admin with the list of corrupted data.

[Get Database Measurements](https://docs.opsmanager.mongodb.com/v4.2/reference/api/measures/get-database-measurements/) currently provides information from dbStats.

Adding collection level statistics would be useful for gathering information via the API on a regular basis to measure growth of each collection and other metrics. Data Explorer functionality is not available via the API.

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.

Integration with Rocket.Chat like done in Slack.

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.

When restoring a snapshot through Ops Manager, automation will create the config file for you. But if you're restoring a snapshot manually, there's no config file! Surely we can include a sample mongod.conf withe sufficient information filled out to help a user get up and running again.

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

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

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

All of our hosts are in the same TZ. We would like to be able to set the Ops Manager related logs timestamps to our local TZ.

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.

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.

A very common Enterprise HTTP Proxy configuration is to deny requests from local networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).

In hybrid mode, the Backup Mode attempts to download the binaries from itself locally through the proxy. This brings to errors as the proxy is blocking the local traffic.