Ops Tools
487 results found
-
Make it possible to specify the key names in the Kubernetes Secret containing S3 access and secret access keys when configuring backups
Currently, the expected data key names in the Secrets referenced in the MongoDBOpsManager CR snippet below are hard-coded into the operator as "accessKey" and "secretKey".
apiVersion: mongodb.com/v1 kind: MongoDBOpsManager ... spec: backup: s3OpLogStores: - s3SecretRef: name: mdb-bkp-aws-s3-creds s3Stores: - s3SecretRef: name: mdb-bkp-aws-s3-credsIf the Secret's data key names were configurable, it would make life much easier for folks using the OpenShift Cloud Credentials Operator to generate S3 credentials. Maybe the CR could change to look something like this:
apiVersion: mongodb.com/v1 kind: MongoDBOpsManager ... spec: backup: s3OpLogStores: - s3SecretRef: name: mdb-bkp-aws-s3-creds accessKeyDataKeyName: aws_access_key_id s3Stores: - s3SecretRef: name: mdb-bkp-aws-s3-creds secretKeyDataKeyName: aws_secret_access_key1 vote -
atlas online archive inside ops manger on-premise
develop "atlas online archive" inside ops manger on-premise
1 vote -
Add CRD for Trigger Functions.
We would like to create a Scheduled Trigger Function for a federated database instance, and currently the Operator does not support this resouce. Do you have any future plans to support Trigger Functions with the Atlas Kubernetes Operator? Or is there any alternate solution that you would recommend?
1 vote -
Prevent aggregation queries from appearing as poorly targeted queries
When looking at query targeting aggregate group queries can show up incorrectly as poorly targeted. For example if I select all documents with a given client id and group them by null and sum a field (eg revenue) then if there are 1,000,000 documents that get summed up to return 1 agregate document then it considers the query targeting to be 1,000,000 because it scanned 1,000,000 documents and returned one. This is highly misleading however since the query used an index to find the exact 1,000,000 documents needed and then used every single one of those documents to generate the…
1 vote -
Allow alerts based on CPU iowait in OPS manager
Currently, there is no way to set alerts on CPU iowait in OPS Manager. When there's disk latency, cpu iowait usually shows an immediate and consistent spike. Alerting on cpu iowait can enable customers to promptly review and address disk latency.
1 vote -
Add imagePullPolicy to the CRD
I want to set imagePullPolicy for every container created with the Mongo DB Commnunity Operator.
1 vote -
Add Ops Manager UI breadcrumbs to help with user navigation
Breadcrumbs show the user where they are in the Ops Manager's (webpage) hierarchy.
https://www.smashingmagazine.com/2009/03/breadcrumbs-in-web-design-examples-and-best-practices/
1 vote -
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 -
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 -
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 -
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 -
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
- Don't see your idea?