Ops Tools
204 results found
-
Allow scheduling grooms
Add the ability to schedule groom jobs at a specific point in time. Also expose this functionality through the API for easy modifications through configuration management tools.
6 votes -
Support migrations to different snapshot stores
Currently it is not possible to transition between snapshot store types.
There are two options currently when transitioning to the new one.
- Terminate backups (deleting all previous snapshots)
- Create a new project and abandon the previous one to allow automated restores at a later time
Both of these options are difficult to manage for large deployments. The first option requires you to store the snapshots elsewhere and disallows automated restores. The second option requires many operations and clutters the Ops Manager project list.
Ideally we should be able to transition from any store location/type to any other location/type. One of…
25 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.1 vote -
Create Ops Manager API endpoint to download mms0.log files
We should expand the Ops Manager API to provide mms0.log downloads the same way we allow mongod deployment log downloads. This will help users with diagnostics when they deploy many Ops Manager instances via the kubernetes operator but do not yet have centralized logging.
3 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 -
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.
14 votes -
Ops Manager API call for Host Mappings
This feature request is for a new Group/Project API call for the management of the host mappings created in Ops Manager from monitoring information. Whether it be an endpoint for "Reset Duplicates" or full featured create/delete of individual host mappings, both will alleviate issues where overlapping mappings affect monitoring in Ops Manager.
Note: The issue of overlapping mappings may occur when a mongod process has moved/changed IP addresses multiple times. With enough cycling (as seen in Kubernetes clusters with frequent pod restarts), eventually a previously mapped IP address may now be associated with a different mongod process.
8 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 -
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 -
Update automation config through API without pushing entire config file
For updating any Automation managed parameter, the only method through API is involving pushing the entire Automation config (which is a json file of hundreds lines) with modifications/addition all together.
Even though I just want to update one single value.
Is it a bit dangerous that there may be human mistake when modifying such a large json file. Wrong configuration may be push to the server.
Graceful if there is a feature which allow user to partial update the configuration through API.
Ref Case: 00730243
4 votes -
Ops Manager Prometheus metrics
MongoDB Ops Manager would need to expose endpoints for Prometheus for MongoDB Clusters. There are a number of metrics that popular MongoDB Exporters do not provide, for example:
1. Enterprise Backup status
2. Replication Alarms
3. Agent statuses
4. A number of Cluster statuses
etcThere is no way to get this data into Prometheus at the moment
7 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 -
I want to auto scale vertically and horizontally nodes cpu or disk in Ops Manager
As a DBA using Ops Manager, I want to auto scale vertically and horizontally nodes cpu or disk when certain thresholds are met. As of right now, there is no auto scale functionality in Ops Manager.
1 vote -
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 -
Only download to /mms/mongodb-releases/ those versions actually in use in a deployment
/mms/mongodb-releases/ is continually updated with the most current minor release of each major version which can fill the partition.
This request is for "Only download to /mms/mongodb-releases/ those versions actually in use in a deployment"
eg if I am only using 4.2.20 in my actual deployments only download the most recent 4.2.x and not 3.6.x
of course if I do decide to deploy a 3.6.x deployment this FR would need to automatically be bypassed and download my 3.6.x and the most recent 3.6.x.
This request is similar to but not the same as another Feature Request:
Do not download EOL…3 votes -
Support rolling rebuild index
In some particular situation indexes need to be rebuild.
It would be nice to support a rolling index rebuild like Ops Manager does for the standard create index.3 votes -
Encrypt Password LDAP Query User
The LDAP Query user's password appears in plain text in mongod.config file. The ability to mask its password in automation config file using credentialstool would mitigate a security risk.
8 votes -
index review before sharding with OPS Manager
Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
So, several features could exist :
- before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
-…5 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 -
S3 Snapshot Store Speed Test
It is often quite difficult to diagnose latency/bandwidth/generally slow S3 storage. It would be useful if Ops Manager could run a short test to show:
- How fast a single large object can be PUT and GET
- Measure parallel PUTs and GETs against test objects
- How much latency there is between Ops Manager and S3
1 vote
- Don't see your idea?