Ops Tools
464 results found
-
Different networks support in Ops Manager
We need Ops Manager being able to manage our infrastructure architecture.
We have a service network and an operational network. The servers, at the physical level, are located in the operational network with their domain (for example servername.operational.network.net, which is what is in /etc/hosts and what you get when you run "hostname -f") and the replica set nodes, at the MongoDB level, are in the service network (for example servername.service.network.net).
When you try to add an existing MongoDB deployment in Ops Manager, as indicated in the wizard, you must do it with the name…
1 vote -
Operator opsManager.configMapRef as a secret
currently inside the mongodb Operator custom resource
MongoDB, a configMap stores the orgId.
e.g.
apiVersion: mongodb.com/v1
kind: MongoDB
metadata:
name: my-mongodb
spec:
...
opsManager:
configMapRef:
name: my-mongodb-ops-manager-diga-project-configmap
credentials: my-mongodb-opsmanager
please allow storing the orgID inside a secret via:
spec:
...
opsManager:
secretRef:
name: my-mongodb-ops-manager-diga-project-secret
credentials: my-mongodb-opsmanager
1 vote -
Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used t
Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used to store the secret?
1 vote -
Opsmanager API: Include Backup Id in List Restore Jobs Response that restore was triggered for
Hello,
there is already a snapshot id included in the list restore jobs response, BUT the problem arises with sharded instances: If you restore a sharded instance to a specific backup, multiple restore jobs are created (one for config server, one for each shard). Thus, the snapshot id in the list restore jobs response refers to the backup of the single component (either config server or shard) and not to the overall backup of the entire sharded instance the restore was initiated for.
Hence, you cannot map those restore jobs to the backup the restore was triggered for, which makes…
4 votes -
Add support in homebrew for mongosync
Could you add support in https://github.com/mongodb/homebrew-brew for mongosync https://www.mongodb.com/try/download/mongosync
1 vote -
Allow OPS Manager to export as CSV or JSON All projects page information
All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.
Add export as CSV or JSON All projects page information.
Current MongoDB Usage report doesn't fit due:
1. It doesn't report backup, encryption information
2. Cluster name could be not right if the cluster was unmanaged and added back to OPS manager as managed. (Cluster_0 bogus names)1 vote -
Allow to select columns visible on OPS Manager All projects page
All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.
We need ability to select only few columns visible on this page.
Example:
cluster name, data size2 votes -
All projects page in MongoOPS should show if encryption at rest is enabled
All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.
We need to see if encryption-at-rest is enabled.
2 votes -
The Backup Daemon auto downloads all old Mongodb versions
If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
All the old versions take up disk space and can only be deleted if the setting is changed to false.
thanks1 vote -
Publish Ops Manager deployments to Slack
It would be nice if the Slack integration could be used to post deployment notices to a Slack channel.
We have a channel where our other tooling posts about changes that have been made, and there isn't an easy way to have Ops Manager do the same.
2 votes -
Mongo Atlas: create backup before updating version
If I upgrade Atlas cluster, Atlas automatically creates a backup with the new version.
I'd rather have a backup of the cluster with original version.
It will allow to restore to the previous version.
Current workaround: create a backup manually before upgrade.1 vote -
Add a possibility to download all snapshots for deployment/project/organisation
Currently, it is not possible to move between S3 buckets without to terminate the job. It would be great to have possibility to download all the snapshots before to delete backup job.
4 votes -
encryption at rest
Right now there is only option to encrypt the key used to encrypt the database. There is no way we can choose which encryption technology is being used to encrypting the database and its backups. The default protocol being used by mongodb may not align with the security policy of the company.
1 vote -
1 vote
-
Alert for even number of voting members of a Replica Set
Alert for even number of voting members of a Replica Set
6 votes -
mongosync filtered sync update
Currently we cannot modify a filter that is in use without wiping all user data in the target cluster.
For exclusion filters, where we exclude collections NOT to copy, adding more collections to exclude should not require wiping all user data.
This is very cumbersome otherwise.1 vote -
Show better diff for changes to setParameter json blob
The "review and deploy" step only shows that there IS a diff in the setParameter json, but it does not make it clear what is actually changing.
It would be very helpful to show the diff between the two json payloads in an easy-to-read way.
2 votes -
Authentication mode MONGODB-OIDC
Support for authentication: MONGODB-OIDC
security:
authentication:
enabled: true
modes:
- "MONGODB-OIDC"currently we get the following error wir kuberntes operator 1.26.0, OpsManager 7.0.7 and RS 7.0.11:
Unsupported value: "MONGODB-OIDC"9 votesWe're considering this for inclusion into Q4 (by end of January) - but we're currently reviewing priorities for a number of projects competing for attention.
-
mongoimport should explain why documents fail schema validation
Currently, with mongoimport 100.9 and MongoDB 7.0 with schema validation enabled, mongoimport will only report that a document failed to import due to schema validation. It would be useful if it could explain why it violates the schema (e.g. which fields are missing, which datatypes are incorrect, etc.). This is similar to the feature request for MongoDB Compass2
1 vote -
Add specific label to Arbiter deployment to distinguish it label-wise
As per https://github.com/mongodb/mongodb-kubernetes-operator/issues/1442 we would like to request to either and/or:
a) have the operator add a new label to replica and arbiter statefulset deployments to distinguish them from each other
b) have the ability to add your own labels to specifically the replica OR the arbiter statefulset deploymentsHaving the ability to easily filter arbiter statefulsets from non-arbiter statefulsets would be great. This is useful for example for backup tools that run commands on pods based on a combination of labels, to exclude any arbiters from backup.
3 votes
- Don't see your idea?