Ops Tools
230 results found
-
Webpage session expiry - introduce inactivity timeout
Currently one can specify a "Session Max Hours" - The number of hours before a website session expires and a user must login again.
This should be replaced or enhanced with an "Inactivity timeout".
We have the requirement to set a timeout due to PCI.
However with the current implementation I have to re-login to the website even when working actively with OPS Manager. An inactivity timeout would allow to be logged out when I am not working on the OPS Manager, but not whilst working with it.4 votes -
Binaries should be provided via Docker images
To implement this in a Kubernetes native way for offline deployments, the binaries should be provided as Docker images and distributed through the Docker repositories that are already present in the k8s environment.
Option 1 (intermediate): Allow Mount of Docker images in the MongoDBOpsManager resource for the path defined in automation.versions.directory. This would allow us to pre-package the binaries needed and bring up the OpsManager in a kubernetes native way. Everything else (e.g. agent downloading the tgz) would stay the same and still be the "OpsManger-way".
Option 2 (long term): The MongoDB TGZ package is provided as Docker image by…
5 votes -
job scheduling from Ops Manager
Please provide job scheduling from Ops Manager, should be able to run Database jobs and non database jobs, shows history of jobs, options to purge job history.
2 votes -
Provide a feature to monitor the Alert payload being sent out from Ops Manager to the configured Webhook endpoint and etc.
What is the problem that needs to be solved?
Provide a feature to monitor the Alerts payload being sent out from Ops Manager to the configured Webhook endpoint and other AlertsServices endpoint.Why is it a problem? (the pain)
Currently, Ops Manager does not log the successful/failed payload of the Alerts being sent out to the configured Webhook endpoint. It is difficult to diagnose the problem with the configured Alert Services.2 votes -
Add collection level statistics to the measurements API
Get Database Measurements currently provides information from dbStats.
Adding collection level statistics would be useful for gathering information via the API on a regular basis to measure growth of each collection and other metrics. Data Explorer functionality is not available via the API.
7 votes -
Plugin for Moogsoft monitoring tools.
Currently, Ops Manager does not have the plugin for Moogsoft monitoring tools, it would be great to add the feature to the future release of Ops Manager.
3 votes -
Create localhost exception for POST /unauth/users API call
The purpose of this request is for Ops Manager to implement a "localhost exception" for the API call POST /unauth/users so it can only be executed under two conditions:
1. No other users exists in the setup.
1. Ops Manager runs in "invitation only" mode.
1. Ops Manager has not been configured for LDAP.
1. The API call can only originate from an IP or alias that belongs to one of the Ops Manager Application server.2 votes -
ability to re-order alerts
when you add new alert there is no way in GUI to order/reorder them. It's hard to maintain large set of alerts.
4 votes -
MongoDB Agent alters the root $PATH variable
The MongoDB Agent installation via RPM adds the /var/lib/mongodb-mms-automation/bin to root's $PATH by placing the mongodb-mms-automation-agent.sh script under the /etc/profile.d:
$ pwd
/etc/profile.d
$ sudo cat mongodb-mms-automation-agent.sh
export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}This breaks my customers security standards.
Moving the script does not appear to affect the functionality of the MongoDB Agent and updating the agent via the OM UI does not add back the script.
We would like the ability to either select the contents of the MongoDB Agent rpm or be asked during the rpm installation whether or not to install the mongodb-mms-automation-agent.sh script.
2 votes -
Allow configuring custom builds at the organisation or global level (Admin panel)
It must be done at the project level at the moment, generating an operational costs for those environments with a large number of projects.
2 votes -
Ability to customize subject line for System & Global Alerts
Currently there's no way to customize the subject line of either a system or global alert. The subject line only has the project name & time. It doesn't even say why the alert was generated until the email alert is opened. Having the ability to modify the subject line, even if it's to certain predefined fields such as alert condition for example would be helpful in addressing alerts in an efficient and effective manner.
7 votes -
Provide safety mechanism for limiting MongoDB versions amongst different projects
Restrict the user depending on the type of project: dev, prod, etc to select a specific set of MongoDB Server versions that can be deployed.
Prior to 4.2 this was accomplished with version manager.
2 votes -
Periodically notify users of unused versions located in versions directory
As a safety measure for admins in Ops Manager to avoid facing issues due to unnecessary disk occupation under the Ops Manager installation directory:
Send periodic notifications (configurable) i.e: once a month; to notify what binaries are not being used by none of the components in their environment so they can evaluate to delete them in order to free up space on their Ops Manager servers.
5 votes -
Apply Project Maintenance Windows to Global Alerts
Apply Project Maintenance Windows to Global Alerts
Make the existing Project-level maintenance windows also silence Global alerts associated with the Project.
We have many projects that share the Global Alerts and do not want to turn off all global alerts as we still need that alerting for the projects that are not being worked on.
In combination with the existing API for Project Maintenance Windows, this really allows full control.
13 votes -
Allow configuring Ops Manager to ignore proxy for internal requests
A very common Enterprise HTTP Proxy configuration is to deny requests from local networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
In hybrid mode, the Backup Mode attempts to download the binaries from itself locally through the proxy. This brings to errors as the proxy is blocking the local traffic.
4 votes -
Ops Mgr "Insufficient oplog size" is confusing and prevents backups
When using Ops Manager UI (I've not checked the API) to declare a MongoDB cluster to be backed up, Ops Manager tries to be a good citizen and check to see if the clusters oplogs are large enough, based on their recent usage to hold at least 3 hours worth of data based on the last 24 hours of usage patterns. if the check fails, the user is prevented from enabling backup and is shown the warning:
"Insufficient oplog size: The oplog window must be at least 3 hours over the last 24 hours for all members of replica set…
2 votes -
restore
it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.
5 votes -
Add hostname/port attributes into all Cluster/Replica Set alert types
What is the problem that needs to be solved? Add hostname/port attributes into all Cluster/Replica Set alert types generated via SNMP Alert Traps, Ops Manager's Public API calls (Project/Global Alerts) and Alert Webhooks (Project/Global Alerts).
Why is it a problem? (the pain) Hostname/port attributes are currently missed in Cluster/Replica Set alert types and we only provide a name of the Cluster/Replica Set for which the alert was generated. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see hostname/port information of a Shard/Replica Set for which such alert was generated, in order to quickly understand…
7 votes -
Possibility to send an alert over all/selected alert channels, if all/selected alerts can't be delivered
What is the problem that needs to be solved? Send an alert over all/selected alert channels, if all/selected alerts can't be delivered by Ops Manager's Application Server.
Why is it a problem? (the pain) We can miss an alert (or multiple alerts) from Ops Manager's Application Server if configured alert channel become unavailable since all Ops Manager Alerts are working in fire-and-forget style without any checks/mechanisms to see if the alert was delivered (some alert types can't have that guarantee at all (e.g. SNMP Alert Traps)).
Ops Manager - Alerting Framework.pngflow diagram has been attached to this Feature Request…4 votes -
Add support for collections with default locale
At present if a collection has a default collation configured, sharding such a namespace via Ops Manager results in a failure with the following symptom:
<myCluster_mongos_131> [13:21:17.050] Plan execution failed on step ShardCollections as part of move ShardCollections : <myCluster_mongos_131> [13:21:17.050] Failed to apply action. Result = <nil> : <myCluster_mongos_131> [13:21:17.050] Error calling shardCollection on sh.myColl with key = [[a 1]] : <myCluster_mongos_131> [13:21:14.994] Error executing WithClientFor() for cp=mubuntu:27017 (local=false) connectMode=AutoConnect : <myCluster_mongos_131> [13:21:14.993] Error running command for runCommandWithTimeout(dbName=admin, cmd=[{shardCollection sh.myColl} {key [{a 1}]} {unique false}]) : result={} identityUsed=mms-automation@admin[[MONGODB-CR/SCRAM-SHA-1]][24] : (BadValue) Collection has default collation: collation: { locale: "fr", caseLevel:4 votes
- Don't see your idea?