Incorporate Support CASE management into the OPS Manager, i.e. open a case, upload required traces to the case and maybe even automatically create a support case for some critical problems.... Minimally I'd like to be able to upload required traces directly from sevrer(s) using wget/curl functionality and attach the upload files to the existing support case(s).

Currently one can specify a "Session Max Hours" - The number of hours before a website session expires and a user must login again.
This should be replaced or enhanced with an "Inactivity timeout".
We have the requirement to set a timeout due to PCI.
However with the current implementation I have to re-login to the website even when working actively with OPS Manager. An inactivity timeout would allow to be logged out when I am not working on the OPS Manager, but not whilst working with it.

Please provide job scheduling from Ops Manager, should be able to run Database jobs and non database jobs, shows history of jobs, options to purge job history.

What is the problem that needs to be solved?
Provide a feature to monitor the Alerts payload being sent out from Ops Manager to the configured Webhook endpoint and other AlertsServices endpoint.

Why is it a problem? (the pain)
Currently, Ops Manager does not log the successful/failed payload of the Alerts being sent out to the configured Webhook endpoint. It is difficult to diagnose the problem with the configured Alert Services.

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.

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.

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

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.

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.

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.

The login page for Ops Manager 4.4+ shows "Email Address" and "Password". While using other login methods such as LDAP, an email address may not be used.

It would be more accurate to say username here.

Since Ops Manager APIs seem to be very similar (if not, the same) as Atlas API, and since Atlas Terraform modules seem to run based on Atlas API, it would be very nice to have Terraform modules for Ops Manager.

It is often quite difficult to diagnose latency/bandwidth/generally slow S3 storage. It would be useful if Ops Manager could run a short test to show:

1. How fast a single large object can be PUT and GET


2. Measure parallel PUTs and GETs against test objects


3. How much latency there is between Ops Manager and S3