Ops Tools
454 results found
-
Ops Manager and Backup infrastracture Disaster Recovery support with K8s Operator
We have carried out tests with MongoDB v1.5.5 K8s Operator and Ops Manager 4.2.18 with Backup infrastructure (S3 Snapshots) in an Openshift 3.11 environment (MongoDB Support case attached).
In this case, a "Disaster Recovery" simulation has been carried out. However, several components created by the Operator had to be restored to obtain a similar state to the one before the "disaster".
Furthermore, it is very likely that the S3 Snapshots will be lost if the process is not completed in a certain manner.
It would be great to have an official approach to deploy/restore an OM resource using MongoDB K8s…
4 votesThere is no current supported mechanism for backing up Ops Manager in a way that guarantees the data. As Ops Manager is itself a backup tool, it's challenging to maintain the integrity of the data in DR scenarios.
For this reason we recommend multi-site high availability for OM and AppDB. This is already possible when running OM on hardware of in VMs, but not currently supported in Kubernetes (unless a Kubernetes cluster is spanning sites).
Later this year (2023) we hope to support OM deployments across multiple Kubernetes clusters - as we already support (in beta) for Replica Sets (full release in April 2023 with Sharded cluster support in May/June 2023). Doing so will reduce the criticality of a OM/AppDB backup solution within Kubernetes.
-
sharding
Should provide sharding feature in community Operator.
4 votes -
Add command for upgrade a cluster
Currently there is no easy way to upgrade a cluster but we need to modify the file describing the cluster and push the full description.
Would be nice to have a command like:mongocli om upgrade --version "4.2.10" --fcv "4.2" MyReplicaset
4 votes -
Allow to create custom roles
Allow to create custom roles for Atlas/CM/OM
4 votes -
Support TLS configuration
Add options to the config file for deploy clusters with TLS enabled.
4 votes -
Changes to Backup Configuration
Ability for changes in a project's Backup Configuration page to take effect without having to terminate and restart backups. Terminating backups removes all existing backups thus exposing an organization to risk. Backups can be stopped and restarted for the changes to take effect but not completely terminate them. This would help when changes are needed into terms of backup daemons, blockstores, types of blockstores, etc.
4 votes -
Add Alert for Projects which are not in Goal State
Add an Alert type that is triggered if a project has not reached the goal state for certain amount of time.
4 votes -
Create AppDB user with backup role to allow execution of mongodump
For the purpose of regularly performing backups of the AppDB using mongodump --oplog.
4 votes -
Ability to send SNMPv3 Alert Traps for configured Ops Manager Alerts
What is the problem that needs to be solved? Ops Manager Alerts should have possibility to send SNMPv3 Alert Traps to configured destinations. SNMPv3 provides better authentication, data encryption and message integrity in comparison to SNMPv2c protocol.
Why is it a problem? (the pain) It is mandatory to use SNMPv3 in many enterprise deployments as SNMPv2c does plaintext community string authentication without encryption (SNMPv3 does MD5/SHA1 hashing for passwords and provides encryption for SNMP data).
4 votes -
Install Managed MongoDB Processes as Services in Linux
In Windows, managed MongoDB processes are installed as services. In Linux, they are not. It would be great if managed processes were installed as services so that system administrators would have better control over startup and shutdown behavior, among other things.
4 votes -
Automation - Improve import for automation when keyfile doesn't match
Starting with MongoDB 4.2 we are able to rotate the internal authentication keyfiles in a rolling fashion with the procedure described here:
https://docs.mongodb.com/manual/tutorial/rotate-key-sharded-cluster/Currently when you import for automation a cluster that is using a different keyfile than the one in the automation config a bouncerestart is triggered. We can avoid it by doing a rolling rotation of the keyfile.
The old keyfile should be kept and the new one appended to it in a rolling fashion. We may have already this implemented for the "Rotate keyfile" feature present in the Security tab page.
4 votes -
Webpage session expiry - introduce inactivity timeout
Currently one can specify a "Session Max Hours" - The number of hours before a website session expires and a user must login again.
This should be replaced or enhanced with an "Inactivity timeout".
We have the requirement to set a timeout due to PCI.
However with the current implementation I have to re-login to the website even when working actively with OPS Manager. An inactivity timeout would allow to be logged out when I am not working on the OPS Manager, but not whilst working with it.4 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 -
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 -
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 -
Allow configuring Ops Manager to ignore proxy for internal requests
A very common Enterprise HTTP Proxy configuration is to deny requests from local networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
In hybrid mode, the Backup Mode attempts to download the binaries from itself locally through the proxy. This brings to errors as the proxy is blocking the local traffic.
4 votes -
Possibility to send an alert over all/selected alert channels, if all/selected alerts can't be delivered
What is the problem that needs to be solved? Send an alert over all/selected alert channels, if all/selected alerts can't be delivered by Ops Manager's Application Server.
Why is it a problem? (the pain) We can miss an alert (or multiple alerts) from Ops Manager's Application Server if configured alert channel become unavailable since all Ops Manager Alerts are working in fire-and-forget style without any checks/mechanisms to see if the alert was delivered (some alert types can't have that guarantee at all (e.g. SNMP Alert Traps)).
Ops Manager - Alerting Framework.pngflow diagram has been attached to this Feature Request…4 votes -
Add support for collections with default locale
At present if a collection has a default collation configured, sharding such a namespace via Ops Manager results in a failure with the following symptom:
<myCluster_mongos_131> [13:21:17.050] Plan execution failed on step ShardCollections as part of move ShardCollections : <myCluster_mongos_131> [13:21:17.050] Failed to apply action. Result = <nil> : <myCluster_mongos_131> [13:21:17.050] Error calling shardCollection on sh.myColl with key = [[a 1]] : <myCluster_mongos_131> [13:21:14.994] Error executing WithClientFor() for cp=mubuntu:27017 (local=false) connectMode=AutoConnect : <myCluster_mongos_131> [13:21:14.993] Error running command for runCommandWithTimeout(dbName=admin, cmd=[{shardCollection sh.myColl} {key [{a 1}]} {unique false}]) : result={} identityUsed=mms-automation@admin[[MONGODB-CR/SCRAM-SHA-1]][24] : (BadValue) Collection has default collation: collation: { locale: "fr", caseLevel:4 votes -
Add Ops Manager's Org ID/Org Name/Project Name into Project/Global Alerts API calls & Alert Webhooks
What is the problem that needs to be solved? Ops Manager's Org ID/Org Name/Project Name attributes needs to be added to Project (
GET /groups/{PROJECT-ID}/alerts) / Global (GET /globalAlerts) Alerts API calls and Alert Webhooks.Why is it a problem? (the pain) Ops Manager's Org ID/Org Name/Project Name attributes are currently missed in Project (
GET /groups/{PROJECT-ID}/alerts) / Global (GET /globalAlerts) Alerts API calls and Alert Webhooks. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see Ops Manager's Organization ID/Organization Name/Project Name in order to quickly understand to…4 votes
- Don't see your idea?