Ops Tools
429 results found
-
Add a variable for set the RS name
Add own variable to set the RS name so that the deployment name can be used to name the pod
1 vote -
Make all metrics used in the Atlas dashboard available for the prometheus integration
Make all metrics used in the Atlas dashboard available for the prometheus integration (https://www.mongodb.com/docs/cloud-manager/tutorial/prometheus-integration/#mongodb-metric-labels).
Also describe how the current Atlas dashboard metrics are build from those.
I'm looking especially for the metrics:
- Max Disk IOPS
- Queues1 vote -
Added features to improve backup performance on filesystem
Currently, the ability to use multiple workers in Ops Manager is only available for S3. If possible adding this capability, or additional enhancements, to filesystem storage would be beneficial.
1 vote -
monitoring opt
Allow to configure startupOptions for monitoring/backup agent logs in yaml for deployments. Similar as we have for AppDB - spec.applicationDatabase.monitoringAgent.startupOptions
1 vote -
Ops Manager should allow to perform restore/recovery on individual replica node
Currently Ops manager automatic restore process does not support restoring snapshots to a single node of a existing replicaSet instead Ops Manager restore snapshots to an existing replicaSet.
This will be require in case any individual replica node down for longer period and oplog overwrite on primary.
Thank You1 vote -
Enable external-dns integration via per-service annotations on each generated service
Currently the MongoDB Kubernetes Operator allows specification of annotations on services created by the operator, but only annotations with the same value across all services. The external-dns operator can create DNS names based on annotations on services. In order to support external-dns integration the MongoDB Kubernetes Operator would need to allow one to specify specific annotations for each generated service.
Current spec for external access services:
externalAccess:
externalService:
annotations:
# Same annotations will be applied on all servicesYou could consider a placeholder/substitution scheme like:
externalAccess:
externalService:
annotations:
external-dns.alpha.kubernetes.io/hostname: mydb-db-<instance number>.mydns.comOr some other way of assigning a per-service annotation…
1 vote -
Add flexibility to disable and enable specific fetures of managing mongodb instance in OPS Manager (like user Sync)
Currently , Mongodb admin can not select to disable or enable feature after put mongodb manageed under OPS Manager. like security control .
Normally , Security control is not mongodb or Ops manager admin's responsibility , which is managed by a enterprice access control team.
1 , In opsmanager , there is not role for security control, like useradmin in mongodb.
2 , When ACCESS control team create role in mongodb. Ops Manager sycn it back.
3 , Opsmanager admin have to be engaged to work with ACCESS control team to complete the task.It is kind of not least…
1 vote -
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.
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 -
Allow drag-and-drop of metric graphs from different replica set members
Our use case is we have a replica set, but the east nodes and west nodes are on disk mounts with different names, so they won't appear on the same line in the Metrics tab. We should be able to drag and drop on a replica set member level, not just the metrics level. This allows more customization of metric graph layout.
1 vote -
“Content-Security-Policy” header
Hello,
We want to add the “Content-Security-Policy” header to the OpsManager/MongoDB answers to increase the security level:
frame-ancestors 'none' (Do not render in frames)
script-src 'self': only loads scripts originating on the site (subdomains excluded)
default-src 'none': recommended for services returning HTML.
Could you please tell us how to set up these elements ?Thank you in advance for your support.
Regards
7 votes -
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.
1 vote -
Documentation: API equivalents for each action on OpsManager
In the documentation, for each action on OpsManager it should be explained how to achieve the same result using the OpsManager API (or an equivalent mongocli command, if it exists).
For example, in the pages describing how to configure Backup stores in the OpsManager UI, it should also be explained which APIs to use (admin/backup).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 -
Use different method for Slack notifications
At the moment in integration manager for Slack there is only option to use obsolete webhook method which allows sending notification to single Slack channel configured for this webhook. There is (not that) new API method https://api.slack.com/methods/chat.postMessage which allows sending notification to multiple channels. This is extremely useful if you for example want to differentiate alerts based on its kind or severity. There is also option to use Webhook method in MongoDB but it doesn't support Slack. So please either add support for new API method or make Webhook method supporting Slack so at least two Slack channels will be…
2 votes -
Providing a grafana dashboard for an on-premise cluster
It would be interesting to provide a grafana dashboard when integrating with prometheus.
The documentation is indeed very limited concerning metrics when you're on a mongoDB on premise cluster.
1 vote -
Ability to remove parameter tlsCertificateKeyFilePassword from Advanced configuration
Currently the behavior around this parameter is tricky -once you added this parameter to advanced config - you can't remove it. if you try to remove it - OPS Manager simply ignores this action and when you run "Review and Deploy" - it displays nothing but still let you deploy this "nothing". similar if you want to set the value of this parameter to empty string from something - OPS Manager ignores it and deploy empty list of actions.
the workaround is to remove both tlsCertificateKeyFile and tlsCertificateKeyFilePassword in advanced config, but don't deploy it. then add back tlsCertificateKeyFile parameter…
1 vote -
add clusterId to json output of "cluster list", "cluster describe" commands
currently there is no straightforward way to get clusterId using mongocli. we can get clusterId if we use text format with "cluster list", but not with json.
and with json format we have to use "process list" command, filter out only one process amongst multiple within cluster and filter out clusterId.
it would be useful to add clusterId field into json when we get cluster description from list/describe commands also.
1 vote -
add text option to --output modifier
currently there is no way to format output of command in text format. the only option is to set this format as default in config file and not use --output modifier in specific command. if you rare use text output, you will have to insert --output json in every other commands.
1 vote -
2 votes
- Don't see your idea?