Ops Tools
191 results found
-
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.9 votes -
Option to include hidden secondaries in Replica Set Alerts
As per Replica Set Alerts documentation: "A replica set member is healthy if you run rs.status() for that replica set and the result returns PRIMARY or SECONDARY for that member. Hidden secondaries and arbiters are not counted".
That is convenient when you take hidden secondaries down for backups but we would like include the hidden members in replica set health monitoring.
2 votes -
More admin functionality for backup groom jobs
Currently it is possible to start a groom job, however once the groom is started no additional functionality is available. It would be convenient if a groom could be paused/stopped, if required, on the admin panel.
1 vote -
Restrict snapshot restore download
IHAC who would like to be able restrict snapshot restore download links (by IP / opsman role) to prevent anyone with access to opsman server from downloading. They know about the "number of times the restore link can be used" + "restore link expiration" features but would also like this feature. Please contact me for customer details
2 votes -
Support Cloudian S3 in OpsManager
OpsManager currently supports the S3 implementations of AWS, IBM Cloud and Dell EMC Elastic Cloud Storage. We would like to use our existing Cloudian S3 storage. We've used it for a while now and it works, but we suggest making this an "officially supported" flavor, too.
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 -
In Ops Mgr, provision to create users by deployment rather than by project
Under a project, Now if a user id created, it gets created in all deployments in the projects. Can we have provision to choose which deployment the user gets created.
For example, for project A, we have three deployments rs1, rs2 & rs3. Now under security tab, if we add a users, this user get access to all deployment. can we have a choice which all deployment the user exist.
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…
1 vote -
Include full date/time stamps to OpsManager's logfiles: mms0-startup.log and daemon-startup.log
Currently records in
mms0-startup.loganddaemon-startup.logonly have time stamp in the format:hour:min:sec,milliseconds.
eg.08:28:09,558 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]It would be useful to include the full date/time stamps to each record as currently we can't say to which day do the records refer to.
3 votes -
Add addition authentication mechanisms to the Ops Manager Alerting webhook
Capability to use JWT or SSL certs would be great.
7 votes -
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 regards1 vote -
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 -
Include CPU usage in Sharded Cluster Monitoring Overview
In the sharded cluster monitoring overview it would be useful to also have the option to display the Process CPU usage to quickly identify shards which have a higher CPU load. Other hardware metrics might be useful as well.
4 votes -
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
mongodb1 vote -
Loadbalance functionality for Ops Manager
When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.4 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 -
Improvement of Restore Process in Ops Manager
Presently Ops manager restore process removes all the data from the target MongoDb deployment and then restores from the user selected Snapshot and subsequently applies the PIT restore.
It is noted that time taken by the restore operations increases as and when the DB size increases. The restore operation would also require the Applications to be shutdown and this would lead to increase in Application downtime during the restore process.In order to minimize the downtime we need to reduce the restore time.
One suggestion to reduce the restore time is to perform automated restore from the latest available snapshots…
2 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 -
System Statistics without Automation
Currently it is required to enable automation on a cluster in order to monitor system level statistics such as CPU.
As automation is sometimes not desired for a cluster, please add the ability to gather system level metrics when a cluster is monitored only.
2 votes
- Don't see your idea?