Ops Tools
487 results found
-
OPS Manager should call updateUser to change password to trace it in DB Audit.
If you enable auditing in database, you can't trace change password actions. The reason is OPS Manager updates system.user collection record directly. as a result, this action is not traceble in audit if parameter auditAuthorizationSuccess is not enabled.
But enabling this parameter cause performance degradation as all DML/DDL will be sent through audit layer.
Dropping user at the same time happening as expected and traceable in audit files.
2 votes -
Use different method for Slack notifications
At the moment in integration manager for Slack there is only option to use obsolete webhook method which allows sending notification to single Slack channel configured for this webhook. There is (not that) new API method https://api.slack.com/methods/chat.postMessage which allows sending notification to multiple channels. This is extremely useful if you for example want to differentiate alerts based on its kind or severity. There is also option to use Webhook method in MongoDB but it doesn't support Slack. So please either add support for new API method or make Webhook method supporting Slack so at least two Slack channels will be…
2 votes -
Ops Manager Load Balancer
In the same way we can connect to a replica set via a connection string containing the 3 hostnames of the members (in a 3 member replica set) which indicates some load balancing built in, it would be good to allow automation agent's mmsBaseUrl parameter to accept 3 Ops Manager web app hostnames if Ops Manager was running in 3 nodes on top of a 3 member replica set OM Application DB. With this, if one of the 3 Ops Manager web apps fails, the agent's connection to OM will be uninterrupted. Currently we will have to configure our own…
2 votes -
2 votes
-
Add recommended ulimit settings to the systemctl service definition
The Ops Manager documentation recommends higher than default ulimit settings, so why not include these in the systemctl service definition?
2 votes -
Use additional metadata to differentiate processes
Right now Ops Manager monitoring identifies MongoDB processes according to hostname:port. Unfortunately, if 2 processes have the same short hostname & port in the same Ops Manager project, they'll be treated the same even if they are actually different processes with different FQDN.
Please either allow the use of additional characteristics (FQDN, replica set name, config server name, etc) for differentiating MongoDB processes or provide some way to tag 2 or more processes so monitoring doesn't accidentally miscategorize them as the same process.
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.
2 votes -
Allow configuration of alerts (and setting customer alerts) via enterprise operator
It would be nice to be able to configure an environments alerts directly from the Operator which will be deploying that environment.
2 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 -
Integrating Ops manager with other enterprise tools
Increasing foot print and creating a a smooth integration for customer environment for Mongodb by making it ready to plug and play for any enterprise. Big enterprises will have their own backup, monitoring and automation platforms. Mongodb or ops manager must provide options or may have certifies some enterprise backups or monitoring platforms where customers can seamlessly leverage existing features for backup and monitoring instead of building or testing their own things.
2 votes -
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 -
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 -
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 -
2 votes
-
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 -
Combine Support Portal Mailing Lists when opening cases
Combine different Mailing Lists in the Support Portal, when opening a case. Right now you can use only one Mailing List per case. When opening cases it would be good to choose to send updates to 2 or more mailing lists depending on the audience required. So rather than creating a new mailing list for every possible combination of recipients, choosing more than one mailing list per case, would enable the right people to get updates and reduce the noise for others. E.g. Operations + Project A Mailing list if it only concerns that one project, and Operations + Project…
2 votes -
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 -
Ability to migrate from Ops Manager to Cloud Manager
Clearly users of Ops Manager use it because they have a requirement, keep MongoDB clusters within their own infrastructure.
Well, we have two solutions for that Ops Manager and also Cloud Manager. I personally think if we have automation in the product to move from the Ops Manager control plane to the Cloud Manager control plane it would make it easier for users to take advantage of MongoDB's backup infrastructure and keep updates coming without the hassle of managing it all by themselves.
2 votes -
Ops Manager global actions (mongocli ops-manager admin)
Add cli commands in global scope of Ops Manager to allow for scripting actions on all projects (e.g. update all agents after an upgrade of Ops Manager):
- CRUD projects (prio on get projects to allow for looping over them)
- CRUD orgs
- CRUD users
- global config managemant
- global alert management2 votes -
list who is connected to a cluster
Hello,
On a sharded instance, I try to identify the connected physical people.
It is not easy. I cannot identify my own connection. 😦Can we have a command to find out who is connected to the platform (excluding host2host connections, backup process, ...)?
The closest command but not complete and friendly :
use config
DBQuery.shellBatchSize = 300
db.system.sessions.aggregate( [ { $listSessions: { allUsers: true } },
{ $project: { _id: 0, "user":"$user.name" } } ,
{ $group : { _id: {"user": "$user" }, count: { $sum: 1 } } },
])Regards
Jerome2 votes
- Don't see your idea?