Ops Tools
225 results found
-
Ops Manager - Allow SNMP traps on non standard ports
Allow changing SNMP port from default (162) for customers who run SNMP on non-standard ports.
Currently the port number of the SNMP trap receiver is hardcoded to 162.
2 votes -
Improvements for Datadog integration
Some parameters for Datadog are not configurable in Ops Manager. For example, "tagging". Adding this functionality would make using Datadog easier.
4 votes -
Drag and drop
This is strictly cosmetic, but in Ops Mgr Deployment->Processes->deployment, it would be nice to be able to drag-and-drop the order of the servers. I believe it shows them in the order they were added to the replica set, the same as rs.status() or rs.config() would show, but for our deployments, we typically have 2 "main" systems, and then a third "DR" system. It would be great if I could always have our main systems as the first 2 systems, and then our "DR" system last, regardless of how they were added to the replica set. The order they were added…
1 vote -
The Project Global Admin Agent logLevel settings are redundant and confusing
As explained here:
https://docs.opsmanager.mongodb.com/current/tutorial/manage-project-settings/index.html#admin-project-settingsThe Ops Manager global admins can override the logLevel setting on a project for Automation and Monitoring Agent modules using the webUI.
This will cause the Agent to override the local config logLevel setting to what's set in the webUI.
Please note that this global admin project setting is redundant as the logLevel of the Agent modules can be also set by using the "Edit custom configuration" window in the project agent settings page as explained here:
https://docs.opsmanager.mongodb.com/current/reference/mongodb-agent-settings/#configuration-file-settings-locations1 vote -
As a DBA using Ops Manager, when I make a cluster or project change (eg. enabling LDAP), I'd like to see a "dry run" of potential impact
As a DBA using Ops Manager, when I make a cluster or project change (eg. enabling LDAP), I'd like to see a "dry run" of potential impact like a brief outage so that I will know that this change will have an impact on my end users or not. As of right now, when I make a change, it just happens to all projects/clusters immediately and may create a non-scheduled outage.
1 vote -
I need another level of granularity with RBAC grouping so that only the users of database can see that data.
As a Ops Manager Admin, I need another level of granularity with RBAC grouping so I can have organization, project and subproject permissions. I currently have hundreds of users in a project level and the permissions are too wide.
1 vote -
Allow to generate/download MongoDB Server Audit process logs
Problem Statement,
What is the problem? As of now (2021-03-17) Ops Manager does not support downloading MongoDB Server Audit process logs via UI/API. Atlas does have support for it (viaGET /groups/{GROUP-ID}/clusters/{HOSTNAME}/logs/{LOG-NAME}API call).Why is this a problem? Users needs to be able to download MongoDB Server Audit process logs via Ops Manager, same way as they do for MongoDB Server process logs/FTDC and MongoDB Agent logs (this significantly simplify troubleshooting, when required). Some users require to download MongoDB Server Audit process logs programmatically to store them in Security Information and Event Management (SIEM) system.
Proposal,
* Add MongoDB…4 votes -
Using Ops Manager, I want to get an alert when a collection is a certain size or near no storage so that I can do an investigation
As a DBA using Ops Manager, I want to get an alert when a collection is a certain size or near no storage so that I can do an investigation to see if there is abnormal data growth. As of right now, I can only monitor cluster data size.
2 votes -
Using Ops Manager, Tell me useful information such as "given the current 60 day growth trends, you will run out of space in 2 months"
As a DBA using Ops Manager, I want the system to tell me useful information such as "given the current 60 day growth trends, you will run out of space in 2 months" so that I can do better capacity planning.
2 votes -
I want to auto scale vertically and horizontally nodes cpu or disk in Ops Manager
As a DBA using Ops Manager, I want to auto scale vertically and horizontally nodes cpu or disk when certain thresholds are met. As of right now, there is no auto scale functionality in Ops Manager.
1 vote -
I want control the timing of when that rollout happens on Ops Manager
As a DBA using Ops Manager, when I rollout a cluster or project level change, I want control the timing of when that rollout happens so that I can notify the end users of when an change may occur. As of right now, those changes happen immediately all the entire cluster/project and may create a non-scheduled outage.
1 vote -
Restore a single database within a MongoDB cluster and not store the all the databases in a MongoDB
As a DBA using Ops Manager, I want to restore a single database within a MongoDB cluster and not store the all the databases in a MongoDB cluster so that my restore only impacts a part of my cluster. As of right now, it restores the entire cluster with all database in it.
2 votes -
Able to move a database from one MongoDB cluster to another MongoDB cluster
As a DBA using Ops Manager, I want to be able to move a database from one MongoDB cluster to another MongoDB cluster so I can consolidate databases into a single cluster. As of right now there are no consolidation tools within Ops Manager.
1 vote -
Option to encrypt mms.https.PEMKeyFilePassword in conf-mms.properties file
Currently, credentialstool only offer encryption for username/password for the AppDB mongo.mongoUri.
It would be great to also have the ability to encrypt the mms.https.PEMKeyFilePassword in conf-mms.properties file, so that is not clear text.
1 vote -
1 vote
-
1 vote
-
1 vote
-
Ops Manager plugin support
Provide extension points and documentation for building plugins.
1 vote -
Add compound indexes support for Ops Manager managed Sharding
What is the problem that needs to be solved? Ops Manager Automation does not take into account compound indexes (https://docs.mongodb.com/manual/core/index-compound/), e.g. if we have
{ a: 1, b: 1 }index already exist Ops Manager will still create{ a: 1 }index foraShard Key.Why is it a problem? (the pain) This creates unnecessary indexes with performance impact on the MongoDB Server process.
2 votes -
terminate groom jobs that belong to terminated backup jobs
terminate groom jobs that belong to terminated backup jobs
1 vote
- Don't see your idea?