Ops Tools
436 results found
-
Filter/Sort Process List View
In previous versions of Ops Manager, you could filter the process list page. It would be nice to bring that back, so we could quickly identify processes which do not have recent pings, etc.
3 votes -
adminCredentials secret should always be source of truth for OpsManager
The secret is only taken into account by OpsManager initially when OpsManager is deployed. As soon as the password of this user is changed in OpsManager, this secret is out of sync.
From the docs: "Use these credentials to log in to Ops Manager for the first time. Once Ops Manager is deployed, you should change the password or remove this secret."
https://docs.mongodb.com/kubernetes-operator/v1.4/tutorial/plan-om-resource/#prerequisitesOption 1: This secret should be in-sync with the OpsManager database. Preferably the sync should be from the k8s secret to the OpsManager database.
Option 2: Create a CRD "MongoDBOpsManagerUser" that handles User/Password management for OpsManager similar…
6 votes -
Periodically notify users of unused versions located in versions directory
As a safety measure for admins in Ops Manager to avoid facing issues due to unnecessary disk occupation under the Ops Manager installation directory:
Send periodic notifications (configurable) i.e: once a month; to notify what binaries are not being used by none of the components in their environment so they can evaluate to delete them in order to free up space on their Ops Manager servers.
5 votes -
Collect hardware metrics even if there's no managed mongo process
Collect hardware metrics even if there's no managed mongo process
Have Automation Agent collect hardware metrics on unmanaged mongo hosts.
Automation agents doesn't collect hardware metrics unless there's a managed mongo process. This means we can't provide centralized system monitoring for a heterogeneous environment, where some clusters are running on their own and others are under automation, or on any non-managed host.
8 votes -
To setup number of backup daemons in ops-manager.yaml
In ops-manager.yaml, can we define the number of the initial backup daemons?
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 -
cert-manager & external-dns integration
Since the kube CA integration is deprecated, the operator should have an option to integrate with cert-manager and external-dns for automatic tls and dns records.
1 vote -
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 -
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 -
Provide mechanism for internal password rotation of the automation user
Ops Manager automation currently uses an mms-automation user for node management, but the password for that user is set once and stays forever unless it is updated via the Ops Manager API.
This feature would provide a mechanism that allows this password to be re-generated via the UI or an API call and have it automatically updated on the managed mongod instances as well.
11 votes -
Make the option of "security.TransitionToAuth" available through Ops Manager Advanced Configuration Options
Currently the option of "security.TransitionToAuth" is not available in Ops Manager as "transitionToAuth" is automatically added to each node in a rolling fashion by the Automation agent and then ultimately removed when authentication is finally turned on for all nodes.
Allowing this option through Ops Manager will enable the mongod to accept and create authenticated and non-authenticated connections to and from the connected clients. Thus the clients can use this feature to avoid downtime at their end while the connection settings are updated to use the appropriate user to connect to mongod.
5 votes -
Start MongoDB Agent service (`mongodb-mms-automation-agent.service`) automatically after OS restart, make it default behavior
What is the problem that needs to be solved? MongoDB Agent service (
mongodb-mms-automation-agent.service
) does not start (by default (disabled; vendor preset: disabled
)) automatically after OS reboot.Why is it a problem? (the pain) OS restarts can be frequent, and current default behavior (
disabled; vendor preset: disabled
) of MongoDB Agent not to start after OS restart causing additional downtime for customers.3 votes -
It would be perfect, If I have "Credential ID" and "Verification Link" for courses that I have completed. Yes, I know, MongoDB provides t
It would be perfect,
If I have "Credential ID" and "Verification Link" for courses that I have completed.
Yes, I know, MongoDB provides this information for professional certified developer, but
Why not for the certificate of completion?
1 vote -
ability to re-order alerts
when you add new alert there is no way in GUI to order/reorder them. It's hard to maintain large set of alerts.
4 votes -
Send alert when RECOVERING node has failed due to being too stale to sync from any available node
Ops Manager users with hundreds or even thousands of replica set members (hosts/nodes) need an alert that indicates a nodes is in RECOVERING state and is too far behind the oplog to recover without manual intervention. This information is present in the
mongod
log file. However, Ops Manager should generate a separate alert for this unique and important state. Without this alert, it is not immediately clear when a user needs take action to bring a replica set back to a healthy state.4 votes -
Enable Ops Manager alerts on any FATAL or ERROR lines in the mongod/mongos logs
What is the problem that needs to be solved?
All possible error states and failures reported in the
mongod
andmongos
log files are not raised as alerts in the Ops Manager alerting system. This prevents users from configuring alerts on important events in MongoDB deployments.Why is it a problem? (the pain)
For some users specific errors such as FATAL or ERROR lines in the
mongod
log need to be alerted and addressed with urgency. Since the specific high priority event is different for different users, a configurable, string matching (regex) driven alerting system that constantly monitors themongod
…4 votes -
Ability to set snapshotRetentionDays value to 1
Need to be able to retain 1 day backups only or just daily backups. Need to reduce 3 day worth of archive.
1 vote -
mongocli feature request: whitelist with timeout on current ip to allow temporary mongoshell access from temporary locations
Please add a timeout parameter to the mongocli whitelist command.
Presently, we have to login via web browser to enable temporary mongoshell access from temporary locations.2 votes -
Snapshots taken by Ops Manager Backups should include config file
When restoring a snapshot through Ops Manager, automation will create the config file for you. But if you're restoring a snapshot manually, there's no config file! Surely we can include a sample
mongod.conf
withe sufficient information filled out to help a user get up and running again.6 votes -
alert when one or more monitoring agents in a project fail (not only when there are no agents left)
alert when one or more monitoring agents in a project fail (not only when there are no agents left)
1 vote
- Don't see your idea?