Ops Tools
221 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 -
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 -
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 -
restore
it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.
4 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.png
flow 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 -
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 -
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 -
Federate different Ops Manager instances
When multiple Ops Managers are running across multiple environments it is difficult see the overall picture.
A a federated dashboard that can provide a view into different environments, see overall list of clusters and some basic information about them.4 votes -
Add an option to GUI to rotate Certificates
Add an option to GUI to rotate Certificates for each or all instances of replicaset for MongoDB.
Should include options:
1) rotate certificates for one instances on one server.
2) rotate certificates for all instances belonging to a replicaset.
3) rotate certificates for all instances on one server.
4) rotate certificates for all instances on all servers for a project.3 votes -
clear text password for mongodb ldap authorization
Add the feature to Encrypt the queryPassword parameter for LDAP in the config file directly via Ops Manager , so that text password should not be present in config file.
Keeping direct password is a security concern.
Sample format of the config file:ldap:
authz:
queryTemplate: '{USER}?memberOf?base'
bind:
method: simple
queryPassword: <Password>
queryUser: <username>
servers: serevername:port
transportSecurity: tls
userToDNMapping: '[ { match : "xxxxx)))"
} ]3 votes -
Ops Manager API should be authenticated via Certificate
Ops Manager API uses HTTP Digest Authentication, this method requires a username and a password which are hashed and provided in the form of registered Ops Manager account, and the password which is a Public API Key associated with that account.
But as part of security feature we should be allowed to use Authentication based on SSL certificates as we are using for Client connection, This will help to secure the self automation process if we are developing any internally.
3 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.
3 votes -
Include full date/time stamps to OpsManager's logfiles: mms0-startup.log and daemon-startup.log
Currently records in
mms0-startup.log
anddaemon-startup.log
only 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 -
Profiler and Performance Advisor without Automation
Currently it is required to enable automation on a cluster in order use the Profiler/Performance Advisor.
https://docs.opsmanager.mongodb.com/current/tutorial/profile-database/
https://docs.opsmanager.mongodb.com/current/tutorial/performance-advisor/
As automation is sometimes not desired for a cluster, please add the ability to Profile Databases and use Performance Advisor when a cluster is monitored only.
3 votes -
Ops Manager: add LDAP timeout options
Our LDAP server is quite slow, so we sometimes get technical errors when trying to log in our Ops Manager instance.
We would need add an option to set LDAP server response timeout on Ops Manager side. It could be
mms.ldap.timeoutMs
.(I'm refering to Ops Manager authentication, not to MongoDB deployement authentication)
3 votes -
Create Ops Manager API endpoint to download mms0.log files
We should expand the Ops Manager API to provide mms0.log downloads the same way we allow mongod deployment log downloads. This will help users with diagnostics when they deploy many Ops Manager instances via the kubernetes operator but do not yet have centralized logging.
3 votes -
Only download to /mms/mongodb-releases/ those versions actually in use in a deployment
/mms/mongodb-releases/ is continually updated with the most current minor release of each major version which can fill the partition.
This request is for "Only download to /mms/mongodb-releases/ those versions actually in use in a deployment"
eg if I am only using 4.2.20 in my actual deployments only download the most recent 4.2.x and not 3.6.x
of course if I do decide to deploy a 3.6.x deployment this FR would need to automatically be bypassed and download my 3.6.x and the most recent 3.6.x.
This request is similar to but not the same as another Feature Request:
Do not download EOL…3 votes -
Support rolling rebuild index
In some particular situation indexes need to be rebuild.
It would be nice to support a rolling index rebuild like Ops Manager does for the standard create index.3 votes -
Ops Manager Base URL should support custom paths/sub-directories
It may be desired to place Ops Manager behind a proxy or load balancer based on a URL path (aka sub-directory or prefix). For example, an nginx location may want to proxy pass connections to Ops Manager on "location /opsmanager"
Currently, the Ops Manager Base URL appears to only accept and use the scheme, hostname/domain, and port. Additional path details are ignored by redirects sourcing from javascript functions and html links/resources.Current workarounds require a unique/dedicated server name for proxying or load balancing to Ops Manager web service(s).
This feature request is for supporting custom URL paths when using Ops…
3 votes
- Don't see your idea?