Ops Tools
231 results found
-
The Backup Daemon auto downloads all old Mongodb versions
If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
All the old versions take up disk space and can only be deleted if the setting is changed to false.
thanks1 vote -
Publish Ops Manager deployments to Slack
It would be nice if the Slack integration could be used to post deployment notices to a Slack channel.
We have a channel where our other tooling posts about changes that have been made, and there isn't an easy way to have Ops Manager do the same.
1 vote -
Alert for even number of voting members of a Replica Set
Alert for even number of voting members of a Replica Set
6 votes -
Show better diff for changes to setParameter json blob
The "review and deploy" step only shows that there IS a diff in the setParameter json, but it does not make it clear what is actually changing.
It would be very helpful to show the diff between the two json payloads in an easy-to-read way.
2 votes -
Identify the snapshot of each project and its size in S3 blockstore
Calculating the storage size consumed by snapshots for each projects deployments for the storage size consumed individually in S3 Blockstore. However, on the S3 snapshot store the data will be stored in the below format which doesn't include any project id to identify the specific project.
s3://bucket_name/0E3AA1971D5CF1CA52F9AF22A4228F10293AE9804D43FBF7EB5DDE38DB06B74A/5b27b0e4083826088f259f28_A s3://bucket_name/1860B12165FB7ED336DDAB9D306EF38E18FCBD36BF695904C497B825F83581DC/5b27b0e4083826088f259f28_A
This feature is helpful for the customers to understand and segregate the storage consumption by each deployments3 votes -
Allow assigning users to an organization via api by adding a bypass parameter
Via the parameter
bypassInviteForExistingUsersit is possible to a add a user to a project.
It is important to also have this feature for the Organization, so please add a parameterbypassOrgInviteForExistingUseror similar to enable this.
Without it, we can not automate the creation of new environments.1 vote -
Management capabilities for trusted CA certificates in the Admin UI
Currently it is a manual process per Ops Manager server to add trusted CA certificates to the Java TrustStore. This store is also overwritten on Ops Manager upgrades.
Similar to the S3 block store option to use a specific CA, it would be useful to manage trusted CA certificates for other endpoints such as HTTPS proxies, webhook alerts, and custom download URLs.
1 vote -
Need an alert for KMIP master key rotation
Currently opsmanager has manual rotation of KMIP master keys.
Enhancement required:
Need an alert from project level to rotate keys when nearing the schedule rotation just like SSL expiration alertsNeed for automation of this key rotation would be helpful. If fails, it needs to revert back changes and alert for human intervention.
1 vote -
Add Public API Endpoint for Backup Snapshot Status
When a snapshot is ongoing, the only location to find information on the current status is in the UI on the backup page for a project.
An API endpoint with the same information as the UI would allow for automation and alerting tools if the snapshot creation is not performing as expected.
1 vote -
Add support for zstd compression in Ops Manager connection string
I just tried to enable zstd on the
mongo.mongoUriconnection string for Ops Manager and it looks like it's not supportedFeb 6 13:53:20 opsmanager1 mongodb-mms[3971104]: An unexpected error occurred during pre-flight checks: com/github/luben/zstd/ZstdInputStream
Feb 6 13:53:20 opsmanager1 mongodb-mms[3971104]: java.lang.NoClassDefFoundError: com/github/luben/zstd/ZstdInputStreamGiven the high network in/out values we see from the mongo underlying Ops Manager, I think zstd is likely to be very effective and helpful!
2 votes -
SAML sign either Response or Assertion in Ops Manager
Ops Manager currently requires both the Response and Assertion to be signed for SAML auth. Our IDMS system cannot authenticate via SAML as it can sign either one or the other, not both. We would like a configurable option in Ops Manager SAML auth to enforce signing of Response or Assertion.
1 vote -
Ops Manager: API endpoint for /databases should not require host
Currently the Ops Manager API to list databases requires a hostname: /groups/{PROJECT-ID}/hosts/{HOST-ID}/databases
It would useful to gather databases on a project or cluster level instead as the databases are the same across replica set members.
1 vote -
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 -
Add a cross reference of all projects and roles to user profile
I must click on projects to display all the projects in my list, click the Users link for a project, then search for my ID to see the roles assigned to my ID.
My idea is to consolidate this information and display it under my user profile similar to the Organization page. 3 clicks display my roles for each project on a single page.
1 vote -
add organisation name to project name when project name is not unique
There are multiple places where we need choose project. for example, to create global alerts we can exclude some projects from this alert.
The issue is project name is not unique and there could be projects with the same name in different organisations. For example, every organisation may have project dev or test.
it comes to the issue that you will see in the list of projects "dev,dev,dev,dev" and you don't understand which one you want to use.
it will be much better to display them in the format "org/project", so the example above would be "org1/dev, org2/dev, org3/dev" which…
2 votes -
Supporting the installation of mongosh in Ops Manager Local Mode
Ops Manager v6.0+ supports installing the new mongo shell (mongosh) to the deployment nodes. This feature is not supported in Ops Manager Local Mode.
It would be convenient to the Ops Manager Automation user if they could upload the mongosh binary to the Ops Manager Versions Directory and Ops Manager will install the binary to the deployment nodes similar to the MongoDB Binary and MongoDB Database Tools.
Currently, the customer with Local Mode needs to manage the installation of mongosh outside of Ops Manager Automation.
5 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)))"
} ]4 votes -
Set log file permissions using Ops Manager
Currently there is no way to set the log file permissions from Ops Manager and the default value is 600. Our organization uses Splunk and with the current settings the Splunk user is not able to read the log files. Config file options such as processUmask and honorSystemUmask can be used to change the log file permissions, but they will also change other files such as journal files, wiredtiger files, etc. The only option we have is to add the Splunk user to our role group in Unix, but this causes a security issue.
1 vote -
OPS Manager should call updateUser to change password to trace it in DB Audit.
If you enable auditing in database, you can't trace change password actions. The reason is OPS Manager updates system.user collection record directly. as a result, this action is not traceble in audit if parameter auditAuthorizationSuccess is not enabled.
But enabling this parameter cause performance degradation as all DML/DDL will be sent through audit layer.
Dropping user at the same time happening as expected and traceable in audit files.
2 votes -
Agent authentication to opsmanager using x509 credentials
Similar to how Opsmanger can use x509 to manage deployments, it should be possible to configure the agents to use x509 credentials to communicate with Opsmanager. This will allow for a more consistent security posture across the whole mongodb/opsmanager stack. It would also simplify security procedures such as credential rotation by unifying the authentication mechanism.
This will be an alternative to the existing API Key approach https://www.mongodb.com/docs/ops-manager/current/tutorial/manage-agent-api-key/index.html
1 vote
- Don't see your idea?