Ops Tools
465 results found
-
Allow Ops Manager Data Explorer to read from Secondary nodes
Ops Manager should allow Data Explorer to be configured with a Read Preferences and maxTimeMS options. Not having these options allows this tool to potentially trigger un-optimized queries to only hit primary nodes, which for high load production environments may cause un-expected problems.
2 votes -
Add filters to Global alert screen in Ops Manager
Add a filter for Global alert Configuration Page. It would be nice to have the ability to search for the specific alert to see if you have it configured and for which environments.
A filter similar to what is seen on the "Open Alert" view would be sufficient.
Since we are managing upwards of 50 deployments via Global Alerts this would be a useful feature.
2 votes -
Add backup database monitoring in Ops Manager
Version 4.4 has support to monitor the App DB. Please add the ability to monitor the backup database as well.
2 votes -
Allow Ops manager to downgrade FCV
Ops Manager UI (4.0 -4.4) does not allow downgrading of Feature Compatibility Version (FCV), once the FVC has been upgraded to a higher version. Ops Manager automatically
removes the lower version from the supported FCVs once upgrade completes. But the cluster deployment allows downgrading one level using shell commands. This limitation makes it difficult when planning an upgrade as regression process are more difficult.
We are in the process of upgrading the environment from 4.0 to 4.4 (which requires an intermediate upgrade to 4.2.). So the downgrade process is so difficult with Ops Manager UI.2 votes -
Automated rotation of the Keyfile
Hello,
I have an idea about the Keyfile rotation. So actually you can rotate the Keyfile only through the ops manager manually. But I would recommend to do this automatically with an API. This would help us alot since we have alot of mongoDB instances and this would save alot of time.
2 votes -
Login Page for Ops Manager
The login page for Ops Manager 4.4+ shows "Email Address" and "Password". While using other login methods such as LDAP, an email address may not be used.
It would be more accurate to say username here.
2 votes -
Add MongoDB user discovery via the API
For users running DBaaS MongoDB products powered by Ops Manager automation, it would be useful if the API provided a way to replicate the cluster import behavior where MongoDB users are automatically discovered. This would help in scenarios where an existing Ops Manager deployment fails, and hundreds of deployments need to be moved to a different Ops Manager without knowing what MongoDB credentials the end user of that deployment had created. Having this API would allow the DBaaS provider's own scripting/automation to orchestrate moving these deployments to a new Ops Manager stack with reduced downtime.
2 votes -
update monitoring & backup agent credentials via automationConfig API instead of separate API calls
Right now if you want to change the credentials for the monitoring agent or the backup agent, you've got to make separate API calls. Why not make it so that you can specify everything at once in the same automationConfig API PUT?
2 votes -
Ability to deploy blockstore in "backing database" type organisations/projects
New versions of Ops Manager have the ability to monitor the ApplicationDB in a organisation/project with the "backing database" server type (https://docs.opsmanager.mongodb.com/master/reference/config/ui-settings/#mongodb-usage).
It is common to co-host the blockstore/oplogstore database on the same servers as the ApplicationDB and I would like to deploy these using OpsManager automation but there is a problem because:
* you cannot deploy new clusters in projects with the "backing database" server type
* an agent is tied to a single Ops Manager projectI have two options at the moment:
1. Install a secondary agent on the servers to allow me to deploy…2 votes -
Ops Manager - Allow SNMP traps on non standard ports
Allow changing SNMP port from default (162) for customers who run SNMP on non-standard ports.
Currently the port number of the SNMP trap receiver is hardcoded to 162.
2 votes -
Document list of Alert conditions that post to the Activty Feed but not Alerts page
Document list of Alert conditions that post to the Activty Feed but not Alerts page
It seems like some "non-actionable" alert/event conditions (example: Host has Restarted) post to the Activity Feed but not the Alerts Page.
Notifications are sent.
I cannot find a list of these that post only to the Activity Feed so it would be nice to have them documented.2 votes -
Warn if deploying changes will require a rolling restart
When reviewing changes in automation, warn if deploying changes will require a rolling restart.
As an example, look at the documentation for server parameters. Many parameters include the description "You can only set THIS during start-up", but the the warning that setting this parameter necessitates a restart is missing from Ops Manager (or Cloud Manager).
2 votes -
Using Ops Manager, I want to get an alert when a collection is a certain size or near no storage so that I can do an investigation
As a DBA using Ops Manager, I want to get an alert when a collection is a certain size or near no storage so that I can do an investigation to see if there is abnormal data growth. As of right now, I can only monitor cluster data size.
2 votes -
Using Ops Manager, Tell me useful information such as "given the current 60 day growth trends, you will run out of space in 2 months"
As a DBA using Ops Manager, I want the system to tell me useful information such as "given the current 60 day growth trends, you will run out of space in 2 months" so that I can do better capacity planning.
2 votes -
Restore a single database within a MongoDB cluster and not store the all the databases in a MongoDB
As a DBA using Ops Manager, I want to restore a single database within a MongoDB cluster and not store the all the databases in a MongoDB cluster so that my restore only impacts a part of my cluster. As of right now, it restores the entire cluster with all database in it.
2 votes -
Delete indexes by Cloud Manager API
With the Cloud Manger API it is possible to create new indexes. But there is no possibility to delete indexes by the Cloud Manger API.
2 votes -
avoid generating alert with error message if one oplog node in replicaset got rebooted.
currently if one of the node in appdb/oplogdb goes down for any reasons (for example, linux patch rebooting the node), ops manager generates alert
"Ops Manager was unable to connect to this database and run the
pingcommand. The database could be down, unreachable, or running with authencation and Ops Manager does not have adequate permissions."there are still 2 other running nodes in replicaset. so this alert is misleading and generates false alarms.
2 votes -
Add compound indexes support for Ops Manager managed Sharding
What is the problem that needs to be solved? Ops Manager Automation does not take into account compound indexes (https://docs.mongodb.com/manual/core/index-compound/), e.g. if we have
{ a: 1, b: 1 }index already exist Ops Manager will still create{ a: 1 }index foraShard Key.Why is it a problem? (the pain) This creates unnecessary indexes with performance impact on the MongoDB Server process.
2 votes -
Enablement of Ops Manager Auditing similar to MongoDB's
Hi all
We would like to enable auditing for activities in Ops Manger itself, getting the information directly using the default audit logging options (filesystem / syslog).
Currently we are getting the detailed information in OpsManager, we get some information in the audit.log log when config changes are made via Ops Manager, but not in detail what exactly had been modified in the log files.
To establish a holistic, company wide auditing spanning over all levels (OS / DB / Application) taking use of standard auditing tools this would be highly beneficial.
Regards, Roger
2 votes -
Option to clear deleted alerts
Deleted alert definitions pile up in the "deleted alerts" tab of Ops Manager.
This information may be useful for auditing purpose, but in the long run, the number of deleted alerts may grow too large. Especially in our use case, where alert configurations are deployed through a script that deletes/recreate all alerts.
Feature suggestion: add an action to clear all deleted alerts (or better: clear all deleted alerts older than N days).
2 votes
- Don't see your idea?