Currently, the Ops Manager UI under Continues Backup only shows the following information about the snapshots:
- Replica set name
- Status
- Last Snapshot
- Last Oplog Slice

It would be very helpful to also see:
- Start date/time
- Finish date/time
- Backup duration
- Snapshot size

In some particular situation indexes need to be rebuild.
It would be nice to support a rolling index rebuild like Ops Manager does for the standard create index.

When Ops Manager is in "Local Mode", a system administrator must manually populate the mongodb-releases directory.

Please consider adding a GUI for uploading the releases over HTTP(s) from the Ops Manager admin panel. This will alleviate server access restrictions/issues, as well as provide a quick method of populating the releases from a workstation in an internet restricted environment.

This could be useful for testing SMS messages and twilio integrations.

This feature request is for a new Group/Project API call for the management of the host mappings created in Ops Manager from monitoring information. Whether it be an endpoint for "Reset Duplicates" or full featured create/delete of individual host mappings, both will alleviate issues where overlapping mappings affect monitoring in Ops Manager.

Note: The issue of overlapping mappings may occur when a mongod process has moved/changed IP addresses multiple times. With enough cycling (as seen in Kubernetes clusters with frequent pod restarts), eventually a previously mapped IP address may now be associated with a different mongod process.

MongoDB Ops Manager would need to expose endpoints for Prometheus for MongoDB Clusters. There are a number of metrics that popular MongoDB Exporters do not provide, for example:
1. Enterprise Backup status
2. Replication Alarms
3. Agent statuses
4. A number of Cluster statuses
etc

There is no way to get this data into Prometheus at the moment

It would be good if mongodb university offers Ops manager course like other courses. It will help to understand architecture and moving parts in Ops manager.

WE have a 4 node replica set and when we removed 2 of the nodes at one time the election process didn't know how to elect a new primary. We would like the election process to accommodate an even number of replica set nodes.

Disable the dropdown to add Agent functions on hosts that don't have the MongoDB Agent installed and were only imported for Backup/Monitoring.
The elipsis (...) selections to add Monitoring & Backup Agent functions are available on hosts without the MongoDB Agent. If selected the function appears on the host as grey and standby. This is misleading. The options should not be available on hosts without the MongoDB Agent.

On Servers Page, Activate/Deactivate Monitoring/Backup module should be activated. So that multiple monitoring module should be activated for hot stand by.

When requesting Audit events using the Public API Global events,
not all events provide the Remote Address and Remote Port.

some commands like "find" does present the Remote Port/IP, but others such as updateDocument, insertDocument and deleteDocument do not.

the info is there so why some events present it and some don't?

is it possible to formulate a unify base fields for all events that will include the Remote Address, Remote Port?

Thanks

I have a 3-node replica set deployment. When I retrieve the connection string to the cluster via OM UI, it shows a single node connection string

mongo --host ip-10-0-200-4.eu-west-2.compute.internal --port 27017

I expect it should show a connection string which includes all hostnames, or something equivalent, if deployment is a replica set.

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.