Ops Tools
480 results found
-
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 -
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 regards3 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 -
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 -
Allow the use of symlinks within the Ops Manager directory
Sometimes it would be great if we could move the
conf
,tmp
, orlogs
directories to other filesystems and use symlinks so that Ops Manager doesn't have to worry about where the needed file physically are. Right now, Ops Manager refuses to start whenever this sort of redirection is done.3 votes -
Incorrect Agent version Alert/Banner
If someone upgrades from Ops Manager v4.2 -> v4.4 and then downgrades by reinstalling Ops Manager v4.2, there is no Alert or Banner that the Agent is incompatible.
Attempts to modify deployments with this incompatible Agent displays "Initializing Automation for your Deployment" but never actually does anything. It is only after reviewing the Ops Manager logs that you see "Unrecognized field".
It would be helpful if there was a validation check that displays an Alert or Banner that indicates that the version of the Agent is unknown/incompatible. Perhaps something similar to what is displayed after upgrading Ops Manager that will…
3 votes -
Allow disabling Blockstore for assignment through the Ops Manager CRD
By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.
It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.
3 votes -
Allow enable/disable for agent alerts
When we do server patching, we end up receiving agent down alerts for automation, monitoring and backup agents. Those create unnecessary noise and create a real risk of us missing a real alert. We should have ability to disable the agent alerts as part of server shutdown and enable the agent alerts are part of server startup.
3 votes -
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 -
Request Logs - Add timeframe to list of options
While diagnosing historical issues "Request Logs" does not allow for selectable timeframes. As such, for these issues, logs must be manually gathered. Adding an optional timeframe will assist in diagnosing issues much faster.
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 -
Never delete the most recent backup snapshot
When backup snapshots cannot be completed as scheduled, and they are behind, Ops Manager really should NEVER delete the most recent snapshot. For example, if the snapshot retention policy is to take a backup every 24 hours and keep daily backups for 2 days, and weekly backups for 2 weeks, a new snapshot should not automatically expire after 2 days. If backups are not completing for some reason, and it goes 2 days without a successful new snapshot, the most recent daily backups are deleted and we are left with the most recent weekly backup instead. There really should never…
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 -
Ability to configure all destinations for SNMPv2c Alert Traps in a single place
What is the problem that needs to be solved? Ops Manager needs to have ability to configure all destinations for SNMPv2c Alert Traps in a single place (so that single place needs to be updated instead of dozens of individual Ops Manager Alerts).
Why is it a problem? (the pain) In case if there's a change in SNMPv2c Alert Trap destination(s), it becomes effort to change the respective hosts for each of the alert. This process requires some time (unless customer script it via Ops Manager's API) if amount of configured Ops Manager Alerts is high, and the process itself…
3 votes -
Improve backup process with automatic reparation of broken job
Enhance the Ops Manager feature for the detecting of broken processes, validating its sanity, so that Ops Manager could "un-break" processes and start regular backups without any manual intervention.
3 votes -
FCV 4.2 backup snapshot progress description UI issue
In the "Continuous Backup" when a FCV 4.2 backup snapshot is in progress the progress label text can be too long to be displayed:
Sync:
Transferring - Snapshot received XXXMB of YYYMB from zzz/www files over N hrs (xxx kB/s). Overall progress - XX %The CSS currently has
overflow: hidden
so the text that doesn't fit the table cell in the page is hidden.The only way to see the complete status is enlarging the browser window or zoom out the page.
Please improve the page by improving the CSS style of this page, for example by enabling text…
3 votes -
Include Replica Set Horizons in Connect to your Deployment Modal
Clicking on the "Connect to this replica set" should open a modal that includes the Replica Set horizon host and port (if configured) in addition to the host's FQDN. This will help users determine their connection settings without requesting details from the kubernetes cluster administrators that deployed the database.
3 votes -
Make it possible to prevent incessant Automation log messages about unexpected field in process memory metrics map
My automation manager posts an info message about unexpected fields in process memory metrics map every minute. It's polluting my logs. I would like a way to fix the underlying problem or, if it cannot be fixed, then don't tell me about it in the logs.
Here are some examples:
mongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: thp_enabled. Skippingmongodb-data-prod-vm2.cloud.ca 2020-08-05 - 01:10:47 PM info runtimestatsPrinter Unexpected field in process memory metrics map: speculationstorebypass. Skipping
3 votes
- Don't see your idea?