Ops Tools
483 results found
-
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 -
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 deployments7 votes -
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 -
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…
12 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 -
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 -
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 -
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 -
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 conditions for all alerts based on DB/cluster name
We have a need to route alerts based on our database/cluster's impacted instead of having them apply to any in the current project. I know some of them can condition based on host name, which uses the cluster name, but most alert types have no similar option.
Examples would be:
Search Index Build Complete
Search Index Build FailedThese are sent without conditions and even the message does not indicate what cluster they are for (although you can guess based on the collection name provided).
We do not have the option to route these ourselves with a webhook, as the…
8 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.2 votes -
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 -
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 -
Add support to convert a replica set to a sharded cluster in Kubernetes
Currently it is not possible to use Ops Manager UI or Kubernetes Operator to convert Replica Set to Sharded cluster. Error : changed not allowed.
4 votesPlanned - we have a requirement to have this completed in time for MongoDB 9.0. But no timeline (yet) for delivering this within that timeframe.
- Don't see your idea?