Ops Tools
479 results found
-
Ability to deploy blockstore in "backing database" type organisations/projects
New versions of Ops Manager have the ability to monitor the ApplicationDB in a organisation/project with the "backing database" server type (https://docs.opsmanager.mongodb.com/master/reference/config/ui-settings/#mongodb-usage).
It is common to co-host the blockstore/oplogstore database on the same servers as the ApplicationDB and I would like to deploy these using OpsManager automation but there is a problem because:
* you cannot deploy new clusters in projects with the "backing database" server type
* an agent is tied to a single Ops Manager projectI have two options at the moment:
1. Install a secondary agent on the servers to allow me to deploy…2 votes -
Disable Query Targeting: Scanned Objects / Returned alerts on specific, recurring aggregations.
We run routine, recurring aggregation pipelines (essentially, summing up the values of different categories of transactions) on a 5-minute interval. These aggregation pipelines scan for all objects that match a certain type, then sum the cumulative value of certain values of those objects based on category. This means that we regularly have queries that scan >500,000 objects and consolidate them down to ~12 or so objects that are returned.
In this specific case, I'm alright with the scan/return ratio being very high, and I don't want to be spammed with alerts every five minutes. However, I don't want to disable…
11 votes -
Add ability to transition WiredTiger encryption-at-rest from local keyfile encryption (LKE) to KMIP
If you are using local key file encryption and backing up your MongoDB deployment using Ops Manager, backups won't work correctly if you upgrade to MongoDB 4.2. The correct solution is to switch your encryption to KMIP. But if you try doing that, automation will get stuck!
6 votes -
Allow disabling Blockstore for assignment through the Ops Manager CRD
By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.
It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.
3 votes -
mongorestore from metadata
hi
When start mongorestore, data is restored first.
so, performance is poor, and recovery takes a long time.
would please proceed from the metadata(index) and change it so that it can be restored quickly.as-is: data > metadata(index)
regards,
park1 vote -
connection-pool monitoring
hi
like this, would you please support connection-pool monitoring.regards,
park1 vote -
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 -
Dark theme
Having a dark theme switch in the Ops Manager account personalization settings would be nice!
6 votes -
mongo push
Why doesn't MongoDB provide a tool (integrated or standalone) to operate document migration across on-prem (sharded) clusters? Suggestion might be to officially support tools like "mongo push", which may cover situations of hardware changes, production servers migration, re-sharding.
14 votes -
Allow Webhook notifications for System Alerts
Webhooks are available for Project and Global Alerts. However they are not available for System Alerts.
It would be ideal to be able to use Webhooks for all alerts.
7 votes -
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 -
Document list of Alert conditions that post to the Activty Feed but not Alerts page
Document list of Alert conditions that post to the Activty Feed but not Alerts page
It seems like some "non-actionable" alert/event conditions (example: Host has Restarted) post to the Activity Feed but not the Alerts Page.
Notifications are sent.
I cannot find a list of these that post only to the Activity Feed so it would be nice to have them documented.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 -
Use separate tls.crt and tls.key items in a kubernetes secret for certificates instead of a combined item named server.pem for a MondoDB rep
There should be a way to use separate
tls.crt
andtls.key
items in a kubernetes secret for certificates instead of a combined item namedserver.pem
.We request our certs using cert-manager which generates secrets from the cert CRD and will get auto renewed every so often. These secrets have 2 items,
tls.crt
andtls.key
.So far the only way I have seen to enable tls is to combine these 2 items and rename it into a new secret in kubernetes as item called
server.pem
. This however means that when a cert auto renews that the wrong secret…4 votesSupport for Cert Manager as well as support for separate crt and key is on a roadmap.
We will look into updating our docs to describe cert rotation. -
1 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 -
Warn if deploying changes will require a rolling restart
When reviewing changes in automation, warn if deploying changes will require a rolling restart.
As an example, look at the documentation for server parameters. Many parameters include the description "You can only set THIS during start-up", but the the warning that setting this parameter necessitates a restart is missing from Ops Manager (or Cloud Manager).
2 votes
- Don't see your idea?