Ops Tools
-
Add Ops Manager's Org ID/Org Name/Project Name into Project/Global Alerts API calls & Alert Webhooks
What is the problem that needs to be solved? Ops Manager's Org ID/Org Name/Project Name attributes needs to be added to Project (
GET /groups/{PROJECT-ID}/alerts
) / Global (GET /globalAlerts
) Alerts API calls and Alert Webhooks.Why is it a problem? (the pain) Ops Manager's Org ID/Org Name/Project Name attributes are currently missed in Project (
GET /groups/{PROJECT-ID}/alerts
) / Global (GET /globalAlerts
) Alerts API calls and Alert Webhooks. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see Ops Manager's Organization ID/Organization Name/Project Name in order to quickly understand to…4 votes -
Connect Tab in UI should show a replica set (instead of a host) connection string if deployment is a replica set
I have a 3-node replica set deployment. When I retrieve the connection string to the cluster via OM UI, it shows a single node connection string
mongo --host ip-10-0-200-4.eu-west-2.compute.internal --port 27017
I expect it should show a connection string which includes all hostnames, or something equivalent, if deployment is a replica set.
2 votes -
More fine granular OpsManger roles for API CRUD operations
More fine granular OpsManger roles for API CRUD operations
In order to generate API Keys users need some pretty powerful role https://docs.opsmanager.mongodb.com/current/reference/api/org-api-keys/. Same for project API Keys https://docs.opsmanager.mongodb.com/current/reference/api/project-api-keys/.
Our understanding is that user who can create api keys could also self promote themselves to super admins which is something we don't want and would be a security concern to us. (And admins normally have access to far more things than just user mgmt)
Additionally it would be beneficial to pass in an desired api key - e.g. for initial provisioning and give admins the chance to reset/rotate an…
2 votes -
Incorporate Support CASE management into the OPS Manager, i.e. open a case, upload traces to the case etc
Incorporate Support CASE management into the OPS Manager, i.e. open a case, upload required traces to the case and maybe even automatically create a support case for some critical problems.... Minimally I'd like to be able to upload required traces directly from sevrer(s) using wget/curl functionality and attach the upload files to the existing support case(s).
2 votes -
Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots
Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots
3 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 -
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.2 votes -
restore
it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.
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 -
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 -
Add Global MongoDB Agent Upgrade ability
Add the ability to upgrade all MongoDB Agents across all Projects at the same time instead of clicking on the banner for each Project.
5 votesWe are going to expose this via mongocli first as it would probably makes a fastest solution.
-
Single Project Programmatic API Keys should not require Org User Admin role for IP Whitelists update
When setting a Programmatic API Key in the MongoDB Ops Manager for a given Project, it seems Project Owners are unable after setting the Key to update the IP Whitelist as they require Organization User Admin role to perform such action (screenshot attached).
I guess this makes sense if the same Programmatic API Key is shared between multiple Projects inside the same Organization, but not really if this is applied only to one single Project (i.e. Project Owners should be able to amend the IP Whitelisting of their own API Keys).
I wonder if this could be enhanced in further…
4 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 -
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.
2 votes -
In changing the Pager duty service key at cluster level, this key should automatically be used instead of making changes to each alert
When we migrate from one Pager duty or Slack account to another, as we change the PD/slack service key at cluster level, shouldn't this key get used automatically instead of us going to each alert and recreating the PD/slack entries? It defeats the purpose of setting the PD/slack key at cluster level. And if we have multiple clusters in prod, we will pretty much have to modify alerts for all of them.
The ticket number for reference is Case #00675142
1 vote -
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 -
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 -
Make snapshot retention policy more customisable
Make the retention policy of Ops Manager snapshots customisable so we can choose custom values (like 21) to be more flexible with the settings.
5 votes
- Don't see your idea?