Ops Tools
473 results found
-
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.
-
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 -
Surface Important Project Level Alerts Globally
It is easy to miss global alerts if you are just using the Ops Manager UI and not seeing the emails, or if there is an email delivery issue. In fact, alerts like "Snapshots are behind", which may be days or weeks behind, are not surfaced anywhere in the UI unless you go and dig for them. I suggest adding a count in the top nav bar for critical alerts, or even all alerts.
1 vote -
Allow SSL Cert Rotation Without Restarting The Agent
It would be great if the agent could be sent a signal to pickup a new cert, or detect the cert changed via file watchers, instead of having to restart it.
1 vote -
Separeted mongod and mongodb agent in Kubernetes Operator container
Now both mongod and agent Ops Manager are running in the mongodb-enterprise-database container. Sometimes it becomes necessary to restart the agent separately from the mongodb instance. Now this is impossible to do because systemd does not work in containers
1 voteWe have plans to have the two run separately! Though no firm timeline yet, we're hoping this year.
Right now we have two architectures. The default is a single container that pulls the binaries for the agent and MongoDB server (mongod) from Ops Manager/Cloud Manager. The other is in Private Preview (potential for breaking changes still) and is known as our Static Architecture.
Neither actually runs each in their own containers, and we're hoping to alter the static architecture to make that the case before we release it fully and make it the default.
Aside from restarting one and not the other, this would offer a more intuitive setup when configuring and troubleshooting, and align to a very future proof definition of what "static" means - where security tools are converging on blocking any significant changes to a container between the image and runtime.
-
deployment metadata resync
Ops Manager needs a way to resync deployments' metadata from the console (or command line, or API), rather than direct undocumented CURD operations in AppDB.
My reason for this suggestion:
See Case: 01438273. One of my deployments had duplicate entries for all 3 nodes. We suspect that happened because we were initially using short name hostnames in the deployment's replica set definition and later changed that to FQDN hostnames. The original entries should have been removed from the AppDB collection, but instead they remained there indicating version 4.0.26, while new ones were created, which were then successively updated as the…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 -
we have an ask to use 4 in snapshotIntervalHours
For the api - https://www.mongodb.com/docs/ops-manager/current/reference/api/backup/update-one-snapshot-schedule-by-cluster-id/ we have an ask to use 4 in snapshotIntervalHours. Right now its not supported. Supported ones are - 6, 8, 12, or 24.
Please check and let us know if its possible to add 4 as well to the snapshotIntervalHours
1 vote -
adding comments directly during the Review and Deploy process in mongo
Ops Manager currently does not support adding comments directly during the Review and Deploy process.It is essential to add comments in production environments related deployments to keep track of artifacts (such as incident number or change number) to figure out why the change has been deployed.
Kindly consider adding comments section in review and deployment workflow in ops manager to make ops manager deployments much clear and to have substantial information pon why that deployment is done.
1 vote -
For Mongosync add ability to select write concern.
For Mongosync add ability to select write concern. Especially something along the "all" nodes would be important. Also "custom" one like MultipleDC etc.
1 vote -
Automatically move HEADS in case of backup daemon problem
In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.
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 -
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?
2 votes -
Warn when trying to apply changes that are doomed to fail
Ops Manager UI should show a warning when trying to publish changes while a node is disabled (shut down).
Why ? See this example:
- user publishes a change asking for node 1 to be disabled
- publication is OK, node 1 is stopped by Ops Manager
- user publishes a change asking for node 2 to restart. Ops Manager UI accepts this change...
- ...but publication will fail, with node 2 agent waiting indefinitely for node 1 to get healthyThis is really disturbing because Ops Manger accepts a change it knows it can't deliver.
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 -
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 -
Identify the snapshot of each project and its size in S3 blockstore
Calculating the storage size consumed by snapshots for each projects deployments for the storage size consumed individually in S3 Blockstore. However, on the S3 snapshot store the data will be stored in the below format which doesn't include any project id to identify the specific project.
s3://bucket_name/0E3AA1971D5CF1CA52F9AF22A4228F10293AE9804D43FBF7EB5DDE38DB06B74A/5b27b0e4083826088f259f28_A s3://bucket_name/1860B12165FB7ED336DDAB9D306EF38E18FCBD36BF695904C497B825F83581DC/5b27b0e4083826088f259f28_A
This feature is helpful for the customers to understand and segregate the storage consumption by each deployments5 votes -
Create an option to turn ON/OFF daily snapshots schedule from "Ops Manager- Continuous Backup - Edit snapshot schedule"
Currently, we have the option to take daily snapshots at different intervals (6 hrs, 8 hrs, 12, hrs, 24 hrs) but we do not have an option to not configure daily snapshots. While daily snapshots are considered essential, we have almost 200 replica sets of different DB sizes and the daily snapshots, tend interfere with itself due to large DB size and not completing itself in good time for the next day's daily snapshot to run. So if we turn off the daily snapshot or tune the frequency of the daily snapshots on select large replica sets, we will avoid…
10 votes
- Don't see your idea?