Ops Tools
429 results found
-
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 -
Cloud Manager should offer Feature Compatibility Version setting for new clusters
When creating new clusters in Cloud Manager, there isn't an option to create them with a specific FCV. We just had a need to build a 4.2 cluster with FCV 4.0, and had to do it manually while shutting down automation.
2 votes -
job scheduling from Ops Manager
Please provide job scheduling from Ops Manager, should be able to run Database jobs and non database jobs, shows history of jobs, options to purge job history.
2 votes -
Provide a feature to monitor the Alert payload being sent out from Ops Manager to the configured Webhook endpoint and etc.
What is the problem that needs to be solved?
Provide a feature to monitor the Alerts payload being sent out from Ops Manager to the configured Webhook endpoint and other AlertsServices endpoint.Why is it a problem? (the pain)
Currently, Ops Manager does not log the successful/failed payload of the Alerts being sent out to the configured Webhook endpoint. It is difficult to diagnose the problem with the configured Alert Services.2 votes -
Add collection level statistics to the measurements API
Get Database Measurements currently provides information from dbStats.
Adding collection level statistics would be useful for gathering information via the API on a regular basis to measure growth of each collection and other metrics. Data Explorer functionality is not available via the API.
7 votes -
Plugin for Moogsoft monitoring tools.
Currently, Ops Manager does not have the plugin for Moogsoft monitoring tools, it would be great to add the feature to the future release of Ops Manager.
2 votes -
Grant permission to access Real Time tab to Project Read Only users
Accessing the Real Time metrics tab requires at least the Project Monitoring Admin role but this role has other privileges to administer alerts and manage hosts as well.
It is more appropriate to enable the read-only access user (Project Read Only role) to access the Real Time metrics tab.
4 votes -
Create localhost exception for POST /unauth/users API call
The purpose of this request is for Ops Manager to implement a "localhost exception" for the API call POST /unauth/users so it can only be executed under two conditions:
1. No other users exists in the setup.
1. Ops Manager runs in "invitation only" mode.
1. Ops Manager has not been configured for LDAP.
1. The API call can only originate from an IP or alias that belongs to one of the Ops Manager Application server.2 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 bypass Proxy for the S3 on-prem
Allow configuring Ops Manager to bypass Proxy for the S3 on-prem.
Configuring the S3 Blockstore also respects the Ops Manager Proxy settings. This is not practical if it is the S3 on-prem which typically does not require external (Internet) access.
2 votes -
Send alert when RECOVERING node has failed due to being too stale to sync from any available node
Ops Manager users with hundreds or even thousands of replica set members (hosts/nodes) need an alert that indicates a nodes is in RECOVERING state and is too far behind the oplog to recover without manual intervention. This information is present in the
mongodlog file. However, Ops Manager should generate a separate alert for this unique and important state. Without this alert, it is not immediately clear when a user needs take action to bring a replica set back to a healthy state.4 votes -
Enable Ops Manager alerts on any FATAL or ERROR lines in the mongod/mongos logs
What is the problem that needs to be solved?
All possible error states and failures reported in the
mongodandmongoslog files are not raised as alerts in the Ops Manager alerting system. This prevents users from configuring alerts on important events in MongoDB deployments.Why is it a problem? (the pain)
For some users specific errors such as FATAL or ERROR lines in the
mongodlog need to be alerted and addressed with urgency. Since the specific high priority event is different for different users, a configurable, string matching (regex) driven alerting system that constantly monitors themongod…4 votes -
MongoDB Agent alters the root $PATH variable
The MongoDB Agent installation via RPM adds the /var/lib/mongodb-mms-automation/bin to root's $PATH by placing the mongodb-mms-automation-agent.sh script under the /etc/profile.d:
$ pwd
/etc/profile.d
$ sudo cat mongodb-mms-automation-agent.sh
export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}This breaks my customers security standards.
Moving the script does not appear to affect the functionality of the MongoDB Agent and updating the agent via the OM UI does not add back the script.
We would like the ability to either select the contents of the MongoDB Agent rpm or be asked during the rpm installation whether or not to install the mongodb-mms-automation-agent.sh script.
2 votes -
Allow configuring custom builds at the organisation or global level (Admin panel)
It must be done at the project level at the moment, generating an operational costs for those environments with a large number of projects.
2 votes -
Implement IAM role authentication for AWS SES in Ops Manager
At the moment using AWS SES for email delivery in Ops Manager requires AWS Access Key and Secret Key. Please implement the IAM role authentication for this option as it has been done for the S3 endpoints.
7 votes -
Make the option of "security.TransitionToAuth" available through Ops Manager Advanced Configuration Options
Currently the option of "security.TransitionToAuth" is not available in Ops Manager as "transitionToAuth" is automatically added to each node in a rolling fashion by the Automation agent and then ultimately removed when authentication is finally turned on for all nodes.
Allowing this option through Ops Manager will enable the mongod to accept and create authenticated and non-authenticated connections to and from the connected clients. Thus the clients can use this feature to avoid downtime at their end while the connection settings are updated to use the appropriate user to connect to mongod.
5 votes -
The Get Host, Process, System Measurements Ops Manager API doesn't exactly provides hostInfo.system.memLimitMB.
Add to The Get Host, Process, System Measurements Ops Manager API the hostInfo.system.memLimitMB.
Or add an API to get the pings value.2 votes -
Ability to customize subject line for System & Global Alerts
Currently there's no way to customize the subject line of either a system or global alert. The subject line only has the project name & time. It doesn't even say why the alert was generated until the email alert is opened. Having the ability to modify the subject line, even if it's to certain predefined fields such as alert condition for example would be helpful in addressing alerts in an efficient and effective manner.
7 votes -
adminCredentials secret should always be source of truth for OpsManager
The secret is only taken into account by OpsManager initially when OpsManager is deployed. As soon as the password of this user is changed in OpsManager, this secret is out of sync.
From the docs: "Use these credentials to log in to Ops Manager for the first time. Once Ops Manager is deployed, you should change the password or remove this secret."
https://docs.mongodb.com/kubernetes-operator/v1.4/tutorial/plan-om-resource/#prerequisitesOption 1: This secret should be in-sync with the OpsManager database. Preferably the sync should be from the k8s secret to the OpsManager database.
Option 2: Create a CRD "MongoDBOpsManagerUser" that handles User/Password management for OpsManager similar…
6 votes -
Make Ops Manager credentialstool available for other MongoDB components
This will allow other MongoDB components to encrypt credentials with the use of the same Ops Manager credentialstool: https://docs.opsmanager.mongodb.com/current/tutorial/encrypt-user-credentials/index.html
2 votes
- Don't see your idea?