Ops Tools
441 results found
-
Ops Manager: API endpoint for /databases should not require host
Currently the Ops Manager API to list databases requires a hostname: /groups/{PROJECT-ID}/hosts/{HOST-ID}/databases
It would useful to gather databases on a project or cluster level instead as the databases are the same across replica set members.
1 vote -
reencrypt existing snapshot with new kmip key
Customer may decide to migrate from one KMIP provider to another or from one KMIP server to another. If you need store backups for a long period of time (7 years for compliant reason is not an exception), it becomes difficult to make sure that you can restore snapshots from old keys and all old KMIP servers still up and running.
it turns out that it's not possible to export old keys from one kmip provider and import into another kmip provider due to security reasons.
But at the same time - it looks like much easier to implement option…
1 vote -
Replica Set size Alert
Have an Alert in Ops Manager to notify that a Replica Set is approaching the maximum recommended size (ie: 2TB) and that it should be converted into a Sharded Cluster.
1 vote -
Add a cross reference of all projects and roles to user profile
I must click on projects to display all the projects in my list, click the Users link for a project, then search for my ID to see the roles assigned to my ID.
My idea is to consolidate this information and display it under my user profile similar to the Organization page. 3 clicks display my roles for each project on a single page.
1 vote -
add organisation name to project name when project name is not unique
There are multiple places where we need choose project. for example, to create global alerts we can exclude some projects from this alert.
The issue is project name is not unique and there could be projects with the same name in different organisations. For example, every organisation may have project dev or test.
it comes to the issue that you will see in the list of projects "dev,dev,dev,dev" and you don't understand which one you want to use.
it will be much better to display them in the format "org/project", so the example above would be "org1/dev, org2/dev, org3/dev" which…
1 vote -
Add options to the connection string through the MongoDBUser
We would like to add options to the connection string that is generated by the operator when creating a new MongoDBUser.
The idea is to include these options in the MongoDBUser CRD so the operator can then add them to the connectionString stored in the generated secret.1 vote -
Ability to export/import index definition from mongoexport/mongoimport and/or mongodump/mongorestore
Mongodump/mongorestore and/or mongoexport/mongoimport (whichever makes more sense) should provide an option to export/import only indexes. This would aid in non-conventional migration approaches, moving data to lower environments, etc.
1 vote -
Add a variable for set the RS name
Add own variable to set the RS name so that the deployment name can be used to name the pod
1 vote -
Added features to improve backup performance on filesystem
Currently, the ability to use multiple workers in Ops Manager is only available for S3. If possible adding this capability, or additional enhancements, to filesystem storage would be beneficial.
1 vote -
Ops Manager should allow to perform restore/recovery on individual replica node
Currently Ops manager automatic restore process does not support restoring snapshots to a single node of a existing replicaSet instead Ops Manager restore snapshots to an existing replicaSet.
This will be require in case any individual replica node down for longer period and oplog overwrite on primary.
Thank You1 vote -
Enable external-dns integration via per-service annotations on each generated service
Currently the MongoDB Kubernetes Operator allows specification of annotations on services created by the operator, but only annotations with the same value across all services. The external-dns operator can create DNS names based on annotations on services. In order to support external-dns integration the MongoDB Kubernetes Operator would need to allow one to specify specific annotations for each generated service.
Current spec for external access services:
externalAccess:
externalService:
annotations:
# Same annotations will be applied on all servicesYou could consider a placeholder/substitution scheme like:
externalAccess:
externalService:
annotations:
external-dns.alpha.kubernetes.io/hostname: mydb-db-<instance number>.mydns.comOr some other way of assigning a per-service annotation…
1 vote -
Set log file permissions using Ops Manager
Currently there is no way to set the log file permissions from Ops Manager and the default value is 600. Our organization uses Splunk and with the current settings the Splunk user is not able to read the log files. Config file options such as processUmask and honorSystemUmask can be used to change the log file permissions, but they will also change other files such as journal files, wiredtiger files, etc. The only option we have is to add the Splunk user to our role group in Unix, but this causes a security issue.
1 vote -
Allow drag-and-drop of metric graphs from different replica set members
Our use case is we have a replica set, but the east nodes and west nodes are on disk mounts with different names, so they won't appear on the same line in the Metrics tab. We should be able to drag and drop on a replica set member level, not just the metrics level. This allows more customization of metric graph layout.
1 vote -
OPS Manager should call updateUser to change password to trace it in DB Audit.
If you enable auditing in database, you can't trace change password actions. The reason is OPS Manager updates system.user collection record directly. as a result, this action is not traceble in audit if parameter auditAuthorizationSuccess is not enabled.
But enabling this parameter cause performance degradation as all DML/DDL will be sent through audit layer.
Dropping user at the same time happening as expected and traceable in audit files.
1 vote -
Agent authentication to opsmanager using x509 credentials
Similar to how Opsmanger can use x509 to manage deployments, it should be possible to configure the agents to use x509 credentials to communicate with Opsmanager. This will allow for a more consistent security posture across the whole mongodb/opsmanager stack. It would also simplify security procedures such as credential rotation by unifying the authentication mechanism.
This will be an alternative to the existing API Key approach https://www.mongodb.com/docs/ops-manager/current/tutorial/manage-agent-api-key/index.html
1 vote -
Providing a grafana dashboard for an on-premise cluster
It would be interesting to provide a grafana dashboard when integrating with prometheus.
The documentation is indeed very limited concerning metrics when you're on a mongoDB on premise cluster.
1 vote -
Ability to remove parameter tlsCertificateKeyFilePassword from Advanced configuration
Currently the behavior around this parameter is tricky -once you added this parameter to advanced config - you can't remove it. if you try to remove it - OPS Manager simply ignores this action and when you run "Review and Deploy" - it displays nothing but still let you deploy this "nothing". similar if you want to set the value of this parameter to empty string from something - OPS Manager ignores it and deploy empty list of actions.
the workaround is to remove both tlsCertificateKeyFile and tlsCertificateKeyFilePassword in advanced config, but don't deploy it. then add back tlsCertificateKeyFile parameter…
1 vote -
add clusterId to json output of "cluster list", "cluster describe" commands
currently there is no straightforward way to get clusterId using mongocli. we can get clusterId if we use text format with "cluster list", but not with json.
and with json format we have to use "process list" command, filter out only one process amongst multiple within cluster and filter out clusterId.
it would be useful to add clusterId field into json when we get cluster description from list/describe commands also.
1 vote -
add text option to --output modifier
currently there is no way to format output of command in text format. the only option is to set this format as default in config file and not use --output modifier in specific command. if you rare use text output, you will have to insert --output json in every other commands.
1 vote -
When changing snapshot retention, prompt user to apply new policy to existing snapshots
Currently when you change the snapshot schedule, the changes only apply to NEW snapshots.
Please allow the user the option to apply the new policy automatically to all existing snapshots. Or at the very least, notify them of them of snapshots that exist which do not meet the current policy!
Let me provide an example of the problem. If you have a retention policy of 10 days and on DAY1 you change it to 30 days, your retention will look like this:
DAY1 - 10 snapshots
DAY2 - 10 snapshots
...
DAY10 - 10 snapshots
DAY11 - 11 snapshots
DAY12…1 vote
- Don't see your idea?