Ops Tools
249 results found
-
Benchmark backups in Ops Manager
It would be helpful if, on the Snapshot overview page or on the Admin -> Backup page, there was the ability to benchmark the backup to help identify bottlenecks.
Allow the user to select a deployment to test and then do a random sampling of data (ie: 100MB) to a temporary Snapshot location and then graph out the metrics for things like Memory/CPU/Disk IO on the source host, Database performance, Backup Agent performance, Network throughput, Blockstore/File System Store/S3 write performance, etc.
Then create a report based on this benchmark that can be sent to technical support for recommendations.
This will…
6 votes -
Update automation config through API without pushing entire config file
For updating any Automation managed parameter, the only method through API is involving pushing the entire Automation config (which is a json file of hundreds lines) with modifications/addition all together.
Even though I just want to update one single value.
Is it a bit dangerous that there may be human mistake when modifying such a large json file. Wrong configuration may be push to the server.
Graceful if there is a feature which allow user to partial update the configuration through API.
Ref Case: 00730243
6 votes -
Password policy enforcement
Currently, MongoDB doesn't provide any way to enforce password policies. If there is some way for Ops Manager to enforce a configurable password complexity and age for user accounts managed through Ops Manager, that would be huge win. This can be as simple as adding UI-level validations to the create/edit user form.
6 votes -
Snapshots taken by Ops Manager Backups should include config file
When restoring a snapshot through Ops Manager, automation will create the config file for you. But if you're restoring a snapshot manually, there's no config file! Surely we can include a sample
mongod.conf
withe sufficient information filled out to help a user get up and running again.6 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.
6 votesWe are going to expose this via mongocli first as it would probably makes a fastest solution.
-
custom defined roles In OPS Manager
We need a custom defined role to perform specific functions in the OPS Manager.
For Example --> We need a custom defined role which can perform subset of functions from Project Automation Admin Role + Project Read Only Role + rs.stepDown() functionality
Project Automation Admin Role:
View deployments.
Provision machines.
Edit configuration files.
Download the MongoDB Agent.
+ Project Read Only role.Project Read Only Role:
Activity
Operational data
Ops Manager Users
Ops Manager User roles.** This feature becomes very useful to contain the access of certain privileges and to have the flexibility tailormade privileges instead of giving the…
5 votes -
ops manager agent support for Rocky Linux
Ops manager and Mongodb work on Rocky, but it seems there is no option for Rocky in the Ops Manager agent manifest, the current agent detects no Linux flavor for Rocky Linux. This already works on RHEL/CentOS and Rocky is supposed to be fully compatible with these OS's.
5 votes -
Loadbalance functionality for Ops Manager
When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.5 votes -
Dark theme
Having a dark theme switch in the Ops Manager account personalization settings would be nice!
5 votes -
Reset duplicates button for Ops Manager Admin System overview page
Sometimes customer want to clean up the System Overview page and/or the application db from because:
- They dismissed one or more Ops Manager server running Application servers or backup daemon components
- Their hostnames / domains have changed over the time
- Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the…
5 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.
5 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…5 votes -
index review before sharding with OPS Manager
Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
So, several features could exist :
- before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
-…5 votes -
Project Alert Integration With Rocket.Chat
Integration with Rocket.Chat like done in Slack.
5 votes -
Add 4.4 tool to PATH
Since MongoDB 4.4 the tools are located in another folder that is not included in the automation agent bash profile:
[root@n1 mongodb-mms-automation]# cat /etc/profile.d/mongodb-mms-automation-agent.sh
export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}Would be nice to have also the mongo tools in the path
5 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 -
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 -
restore
it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.
5 votes -
Opsmanager API: Include Backup Id in List Restore Jobs Response that restore was triggered for
Hello,
there is already a snapshot id included in the list restore jobs response, BUT the problem arises with sharded instances: If you restore a sharded instance to a specific backup, multiple restore jobs are created (one for config server, one for each shard). Thus, the snapshot id in the list restore jobs response refers to the backup of the single component (either config server or shard) and not to the overall backup of the entire sharded instance the restore was initiated for.
Hence, you cannot map those restore jobs to the backup the restore was triggered for, which makes…
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.4 votes
- Don't see your idea?