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

Currently Ops Manager CRD deployment requires configuration using GUI which is a manual step. An option completely define all OPS Manager settings / Org in declarative manner via yaml will be great in building completely automated CI/CD Pipelines

Please, build a course like you already have but now for Kubernetes Operator. I had serious troubles implementing it.

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.

For the purpose of regularly performing backups of the AppDB using mongodump --oplog.

The deployment that utilizes __exec setting is unable to import to Automation as well as it is unable to deploy the deployment by Automation with this setting.

In order to separate replication, client and administrative traffic, servers may have multiple network interfaces using different IP and hostname aliases associated with them.

According to the requirements described on https://docs.opsmanager.mongodb.com/current/tutorial/provisioning-prep/#server-networking-access Automation currently can use only the server hostname defined as hostname -f and cannot use any of the other aliases matching to other IP addresses for the other machine host aliases.

Please add some way to customize which host alias Automation should use as a configuration parameter for the Agent.

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.

Clicking on the "Connect to this replica set" should open a modal that includes the Replica Set horizon host and port (if configured) in addition to the host's FQDN. This will help users determine their connection settings without requesting details from the kubernetes cluster administrators that deployed the database.

What is the problem that needs to be solved? MongoDB Agent (Automation Module) doesn't have ability to configure Automation logs compression.

Why is it a problem? (the pain) Current behavior of MongoDB Agent (Automation Module) to not allow to compress its logs is sub-optimal since MongoDB Agent (Automation Module) logs takes more disk space if its logs are kept uncompressed.

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

What is the problem that needs to be solved? Monitoring is down and Backup is down alerts needs to be sent for each individual MongoDB Agent (Monitoring/Backup Module) which become down, Monitoring is down and Backup is down alerts should include hostname information in them.

Why is it a problem? (the pain) Customer can't easily identify which MongoDB Agent (Monitoring/Backup Module) become down without hostname information available in the alert (in multi-project environment this becomes operational pain for the customer).

Prefer to get BigPanda integrated with OpsManager for event correlation .
www.bigpanda.io

Dear Team,

We are looking for an option to set alerts if any of the Ops Manager Application goes down in a HA environment. Being with HA configuration, we at least expect this feature to in place - as currently it looks like that OPS Manager is not aware of its own HA configuration.

Mongo Case: 00723232

Thanks,
Tom

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

Ops Manager currently allows the ability to rotate audit logs based on the threshold settings in the Update MongoDB Log Settings modal but audit.logs do not compress/delete as the mongodb.logs do from the same modal. We would like the ability to either toggle compression/deletion of audit.log in that modal or a separate modal. We think a separate modal would be better since audit.logs may be used for security forensics and require a longer retention period.

To support chaos engineering.

It's still very new and only kube-router is the only "free" one that supports it. But this is great simplify the network configurations to connect to replicas and shards.

Route Sharing is currently supported on Red Hat OpenShift 4.4+

DB Storage metric is not enough for us. We want to know the GROW RATE not the current value. We want to calculate the database used grow rate space regarding, comparing a past value with the current value. The result of the calculation can be positive (grow rate) or negative meaning database space did not grew up in that period. This is important to define tendency and trigger a disk expansion.