Ops Tools
441 results found
-
Migration Guide for OpsManager to enterprise-operator
It would be great to have a migration guide or documentation to help with migrating an existing OpsManager installation to the kubernetes enterprise-operator based installation.
2 votes -
Export Reports and Graphs
OPtions to export the reports and graphs into a PDF or office tool will help Incident Management process to a great extend.
1 vote -
rename action for backup daemon "delete daemon" to "deactivate daemon"
when you press link "delete daemon" on Admin->Backup->Daemons page it "deletes" daemon from this page, but after mongodb-mms.service gets restarted, this daemon comes up again. this link does not delete daemon - it actually deactivate backup daemon. another part for deactivation of daemon is to modify settings for service mongodb-mms to start only mms application without daemon.
1 vote -
trigger a queryable Backup Snapshot restore via Ops Manager public API
We would like to periodically provision queryable snapshots on a programmatic basis (aka Ops Manager public API call) to easily get a consistent dump of sharded clusters in order to put those dumps in a "very safe location". We want to use this as part of a last resort backup strategy. The idea is that a dump is much easier to be restored by a "last resort restore app" compared to the http-downloaded plain data files.
One other option to extract the contents of a sharded cluster would be to use "Long Running Queries" but this cannot be used along…
5 votes -
mongocli - changing server type
There is a missing option to change server type via mongocli. You can list the server type for the project, but not change it.
available option for list:
mongocli om serverUsage projects hosts list --endDate 2020-01-01 --startDate 2021-01-011 vote -
Ops Manager UI estimates backup time and restore
Backups and restore estimation as UI feedback for regular and continuous backups
1 vote -
Deploy Changes without restarting mongod/mongos instance immediately.
Whenever we want to make changes, eg. set a new parameter or add new parameter in configuration (advance configuration options), after we save changes, review and deploy, automation immediately starts applying that change and does a rolling restart.
We need flexibility in restart, means one should have an option to perform immediate rolling restart or defer it to later time. We may apply multiple changes at different times and set one preferred window to restart instance instead of doing multiple restarts.16 votes -
Logging: attr.error field type conflicts
Hey!
We are using fluent-bit to push MongoDB logs to Elasticsearch. When there are already logs in the elastic index, where attr.error is an object, then it does not accept log lines in which this field is a string:
“error”:{“type”:“mapperparsingexception”,“reason”:“object mapping for [attr.error] tried to parse field [error] as object, but found a concrete value”}
There is log with string attr.error:
{“t”:{"$date":“2022-05-13T15:16:31.203+00:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“MirrorMaestro”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017”,“error”:“ShutdownInProgress: Pool for mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017 has expired.”}}
There is log with object attr.error:
{“t”:{"$date":“2022-05-13T15:20:56.857+00:00”},“s”:“I”, “c”:“REPL_HB”, “id”:23974, “ctx”:“ReplCoord-680”,“msg”:“Heartbeat failed after max retries”,“attr”:{“target”:“alerta-mongodb-arbiter-0.alerta-mongodb-arbiter-headless.monitoring. svc.cluster.local:27017”,“maxHeartbeatRetries”:2,“error”:{“code”:93,“codeName”:“InvalidReplicaSetConfig”,“errmsg”:“replica set IDs do not match, ours: 61ea35f29cfd494fef169571; remote node’s: 61eef8589d065c56e61d6e52”}}}…
1 vote -
Multiple webhook URLs
At the moment only one webhook URL can be configured for one Ops Manager project.
It would be nice if multiple URLs could be used to send the alert to different endpoints by using f.e. a delimiter character inside the config.
Thanks and regards3 votes -
Ops Manager to be able to do archiving of Data to a different replica set than you Prod replica set.
To be able to set up Archiving in Ops Manager so you would be able to keep a certain amount of data in Prod and move the rest of to an Archiving replica set.
1 vote -
Sharding
When we create a new collection with a shard key using mongosh the same is not reflected in cloud manager. In cloud manager / ops manager the shard key for the new collection is not seen in the shard tab.
1 vote -
Include "Fetch Time" in Profiler timings
When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.
In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.
Is there a way to configure Profiler to be more realistic,…
1 vote -
Add command for suspending automation
Add command for suspending automation (similar to what we have for unmanage)
1 vote -
Allow MongoDBUser CRD to interact with a MongoDB resource in a seperate namespace
Allow MongoDBUser CRD to interact with a MongoDB resource in a separate namespace in k8s.
The goal is to have different teams deploy their resources (including applications, configmaps, secrets, PVCs, MongoDBUser CRDs etc) into their seperate namespaces, but have all of them share a single MongoDB replicaset in a common namespace such as
mongodb2 votes -
Do not start backups for Sharded clusters unless all requirements are met
With FCV > 4.2, Backups requires the backup module to be activated on at least one member per shard for sharded clusters but it also doesn't stop one from starting backups if the backup module is activated only on one member of the entire sharded cluster, for example, activating the backup module on a single member of the config server replica set and not on any member of the shards allow for one to start backups.
Currently, if backups are enabled and at least one of the Replica sets in the Cluster has a backup module, backups will start for…
1 vote -
Allow Regexp, or other solution, to look for groups in "SAML Group Member Attribute" field
The Ops Manager authentification process through SAML requires that the user's groups are specified in a dedicated SAML attribute sent by the IDP, so the user can connect to Ops Manager.
For this need, our IDP can only provide a field that contains free text. This field can contain many information, and can include special characters. We can add the Ops Manager groups in this field, among the existing text information.
However we need Ops Manager to parse this free field and get the groups information, which is not possible for now.
That's why we would like the implementation of…
4 votes -
Present MongoDB clients metadata on Ops Manager UI
Before MongoDB version upgrades we should verify all drivers compatibility for the new version.
It is sometimes difficult to track all of the drivers used connecting to the deployments. Currently it requires parsing of multiple mongos/mongod logs for client connections or internal code investigations.
Suggestion
It may be beneficial to collect and present clients statistics (version, type, IP) data on Ops Manager.
Maybe this could be a feature that can be toggled on demand.
1 vote -
Virus threat in MongoDB CLI
I am facing an issue when downloading MongoDB CLI on my win10 computer. The Windows virus scanner says there is a "Trojan:Win32/Caynamer.A!ml" in the file I am trying to download and ends the download. Is this threat real?
1 vote -
connection
Ops Manager only shows number of connection. Most DB monitoring tool shows where the connection is coming from and whats being run from the session. This needs to be a part of Ops Manager
1 vote -
Increase maximum retention periof of backups
Currently OpsManager's maximum retention period for backups is 84 months (7 years). We have the requirement to keep 10 years of backups, hence adding some values (96, 108, 120, 132, 144) in the "Store monthly snapshots for... months" in the backup schedule would be helpful. Another option might be to allow custom values (I guess this is the purpose of https://feedback.mongodb.com/forums/924355-ops-tools/suggestions/39441955-make-snapshot-retention-policy-more-customisable)
1 vote
- Don't see your idea?