Ops Tools
488 results found
-
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
mongodlog 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
mongodandmongoslog 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
mongodlog 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 -
Add `serverStatus.uptime` counter info into Metrics
What is the problem that needs to be solved? We already collect
serverStatus.uptimecounter info from each and every MongoDB Server process, so we just need to addserverStatus.uptimecounter info into Metrics so that it will be possible to trackserverStatus.uptimechanges through the time.Why is it a problem? (the pain) If you'd like to calculate MongoDB Server process availability to know for how long your MongoDB Server process(es) was/were up and running, you'll need to analyze MongoDB Server process logs (in case if they are ever available for required period of time) to see last time MongoDB…
8 votes -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 votes -
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.confwithe 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 -
In the event of an integrity check job failure, an alert should be shown on Ops manager UI instead of solely relying on email
Integrity Check Jobs failures get emailed to the configured "mms.backup.alertsEmailAddr" address and logged in daemon.log. This information should also be available in Ops Manager UI so that the user can quickly check before trying any restoration.
5 votes -
restore
it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.
5 votes -
move/copy pagination buttons on top of log screen
when you browse agent logs( automation/monitoring/backup), the size of records is different because some records can take more than 1 line.
as a result pagination buttons < and > at the bottom of the screen have different location on every page -so it's hard and frustrating to find new location of buttons - particularly when you need go through 10-50 pages...but the top of the page is always is on the same place.
it would be nice to implement one of 3 options :
1. add keyboard shortcut to go forth and back between pages
2. duplicate pagination buttons…1 vote -
Add Ops Manager check to prevent making backups of itself (Backing databases - AppDB, Oplog, Blockstore)
Otherwise, an Out Of Memory condition may result and disable Ops Manager.
6 votes -
Plugin for Moogsoft monitoring tools.
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.
3 votes
- Don't see your idea?