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.2 votes
Allow to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps
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.communitycontrols 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).2 votes
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
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.2 votes
Version 4.4 has support to monitor the App DB. Please add the ability to monitor the backup database as well.0 votes
- Don't see your idea?