Ops Tools
429 results found
-
Admin -> organizations pagination of list
On Ops Manager up to 4.4.1 the Admin -> Organizations page shows only 100 organizations and there is no support for paginating the results.
Please improve the page by allowing the user to see more than 100 organizations.
1 vote -
Create AppDB user with backup role to allow execution of mongodump
For the purpose of regularly performing backups of the AppDB using mongodump --oplog.
4 votes -
integration with Mattermost for notifications
It would be good to replicate the integration with Slack but using Mattermost. Mattermost is open source and allows the companies to deploy their own messaging server. Some organizations are moving from Slack to Mattermost for this reason.
2 votes -
Add the ability for the backup daemon to download and validate snapshots
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.
16 votes -
Include Replica Set Horizons in Connect to your Deployment Modal
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.
3 votes -
Ability to send SNMPv3 Alert Traps for configured Ops Manager Alerts
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).
4 votes -
Add 4.4 tool to PATH
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
5 votes -
Disable the dropdown to add Agent functions on hosts that don't have the MongoDB Agent installed and were only imported for Backup/Monitori
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.2 votes -
Send `Monitoring is down` and `Backup is down` alerts for each MongoDB Agent (Monitoring/Backup Module) and include hostname information in
What is the problem that needs to be solved?
Monitoring is downandBackup is downalerts needs to be sent for each individual MongoDB Agent (Monitoring/Backup Module) which become down,Monitoring is downandBackup is downalerts 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).
11 votes -
Activate multiple monitoring module in appDB monitoring project
On Servers Page, Activate/Deactivate Monitoring/Backup module should be activated. So that multiple monitoring module should be activated for hot stand by.
2 votes -
Password policy enforcement
Currently, MongoDB doesn't provide any way to enforce password policies. If there is some way for Ops Manager to enforce a configurable password complexity and age for user accounts managed through Ops Manager, that would be huge win. This can be as simple as adding UI-level validations to the create/edit user form.
5 votes -
Store the type of cloud in profile to shorten the CLI command
MongoCLI current requires the user to type on the command-line if it's an Ops Manager, Cloud Manager, or Atlas. We could store this information in the profile (the file containing the URL and API keys) so the users have less to type.
PS: This applies to all 3 categories - MongoDBCLI with Ops Manager, MongoDBCLI with Cloud Manager, and MongoDBCLI with Atlas - on feedback.mongodb.com and the UI forces me to select only one of them
2 votes -
Attain granularity on the Ops manager backups & restore
Backups:Under a project, in a single cluster we may deploy multiple databases which belongs to different applications that are somehow interlinked in terms of their functionality. Different databases requires different backup strategies, retention periods, and so different snapshot schedules. However, the level of granularity on Ops Manager "Continuous Backup" doesn't match the above requirement.
Restore: How could we restore a single collection, or a database without touching the other databases/collections within a cluster? The restore process that we have today seems to be restoring the whole cluster and not to the level of database/collection. Queryable backup snapshot seems to be…
6 votes -
mongocli feature request : add an option to specify the path to the CA file in the mongocli configuration.
Currently while using mongocli to connect to Ops Manager via https, one needs to add the public CA certificate to local system's trusted certificate store. Please add a parameter in the configuration file where one can specify the path to the local CA file
1 vote -
Make it possible to prevent incessant Automation log messages about unexpected field in process memory metrics map
My automation manager posts an info message about unexpected fields in process memory metrics map every minute. It's polluting my logs. I would like a way to fix the underlying problem or, if it cannot be fixed, then don't tell me about it in the logs.
Here are some examples:
mongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: thp_enabled. Skippingmongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: speculationstorebypass. Skipping
3 votes -
Support __exec setting for the MongoDB deployment in Automation
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.
5 votes -
Install Managed MongoDB Processes as Services in Linux
In Windows, managed MongoDB processes are installed as services. In Linux, they are not. It would be great if managed processes were installed as services so that system administrators would have better control over startup and shutdown behavior, among other things.
4 votes -
Automation should handle multiple hostname aliases for each server
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 -fand 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.
5 votes -
In changing the Pager duty service key at cluster level, this key should automatically be used instead of making changes to each alert
When we migrate from one Pager duty or Slack account to another, as we change the PD/slack service key at cluster level, shouldn't this key get used automatically instead of us going to each alert and recreating the PD/slack entries? It defeats the purpose of setting the PD/slack key at cluster level. And if we have multiple clusters in prod, we will pretty much have to modify alerts for all of them.
The ticket number for reference is Case #00675142
1 vote -
University MongoDB - Provide explicit Shell Address to Databases
In places in the text in different units it says:
"We are connected to the class atlas cluster from Compass".You could please be explicit with what that address is, since if one is coming back after a couple of days break and have forgotten how to connect to Compass or Mango Shell. If a link to that is provided its a lot faster to be back on track.
1 vote
- Don't see your idea?