Ops Tools
440 results found
-
Delete indexes by Cloud Manager API
With the Cloud Manger API it is possible to create new indexes. But there is no possibility to delete indexes by the Cloud Manger API.
2 votes -
mongocli - allow to enable/disable agent modules
As of mongocli version 1.17.0 there is no way to enable monitoring and backup modules for a cloud manager or ops manager project.
You can only query the agents and the modules enabled.
This won't allow you to use mongocli to setup a new project from scratch and will require to use the Cloud Manager or Ops Manager API updating the automation config manually for this purpose.
1 vote -
Add ability to configure Pod Distruption Budget for STS
During maintenance work EKS admins may need to evict nodes. This should not cause outage for MongoDB cluster/replicaset running on these nodes. we can create manually PDB for STS, but it would be nice to have an option to do it as part of MongoDB Kubernetes Operator.
2 votesSupporting Pod Disruption Budget natively is something we do hope to do at some point.
But for now it is still possible by creating the PodDisruptionBudget resource and targeting the deployment using labels. (As per https://kubernetes.io/docs/tasks/run-application/configure-pdb/)
-
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 -
sharding
Should provide sharding feature in community Operator.
4 votes -
Import existing MongoDB deployments
There should be a way to import existing MongoDB deployments with mongocli. This would allow the automated provisioning of Ops Manager instances in cases where MongoDB deployments already exist. In addition we would be able to import the application database of Ops Manager automatically whenever a new Ops Manager instance is installed.
1 vote -
Ops Manager Prometheus metrics
MongoDB Ops Manager would need to expose endpoints for Prometheus for MongoDB Clusters. There are a number of metrics that popular MongoDB Exporters do not provide, for example:
1. Enterprise Backup status
2. Replication Alarms
3. Agent statuses
4. A number of Cluster statuses
etcThere is no way to get this data into Prometheus at the moment
8 votes -
Add support for virtualization volume management in Ops Manager Backup snapshots and restores.
Streaming snapshots during a restore from a blockstore out to the MongoDB Agent cases the RTO (recovery time objective) to grow linearly with the compressed datasize in the largest shard/RS of the snapshot. The RTO of an Ops Manager restore could be very significantly improved by leveraging volume management infrastructure (such as from VMWare) to restore previously acquired snapshots as virtual filesystems (volumes).
22 votes -
Allow Ops Manager to only download specific MongoDB binary packages
We would like to have an option in the Ops Manager UI to select certain MongoDB versions to be automatically downloaded by Automation in order to avoid downloading all major binaries.
It is not good to have several MongoDB binaries using disk space and not being used.
1 vote -
Provide support to update version manifest to Ops Manager that uses local mode
With Ops Manager Local Mode on Kubernetes, the version manifest is required to be updated manually via UI or API.
It would be the best practice to support updating version manifest using a command to the Operator or OM Pods.
1 vote -
Enablement of Ops Manager Auditing similar to MongoDB's
Hi all
We would like to enable auditing for activities in Ops Manger itself, getting the information directly using the default audit logging options (filesystem / syslog).
Currently we are getting the detailed information in OpsManager, we get some information in the audit.log log when config changes are made via Ops Manager, but not in detail what exactly had been modified in the log files.
To establish a holistic, company wide auditing spanning over all levels (OS / DB / Application) taking use of standard auditing tools this would be highly beneficial.
Regards, Roger
2 votes -
Reset duplicates button for Ops Manager Admin System overview page
Sometimes customer want to clean up the System Overview page and/or the application db from because:
- They dismissed one or more Ops Manager server running Application servers or backup daemon components
- Their hostnames / domains have changed over the time
- Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the…
3 votes -
Add two more entries to the sample_training.zips collections
The lab task currently can be solved without paying attention to the difference between the $lt vs $lte and $gt vs $gte operators:
MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gte: 5000,$lte: 1000000}}).count()
11193
MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gt: 5000,$lt: 1000000}}).count()
11193Adding two more documents (one with 5000 and the other one with 1000000 "pop" value) would draw attention to this difference
1 vote -
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 -
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.
-
Encrypt Password LDAP Query User
The LDAP Query user's password appears in plain text in mongod.config file. The ability to mask its password in automation config file using credentialstool would mitigate a security risk.
9 votes -
Sharded Cluster Snapshot Restores - Throttling and Src/Dst Mapping
When restoring a sharded cluster snapshot, provide a means of mapping the source shard replica set names to the target shard replica set names. This will allow users to predictably restore large/small shards to the appropriate target hosts.
Currently, this can be done for sharded clusters with fewer than 10 shards by naming the shards in a predicable shard## pattern. However, greater than ~10 shards leads to an alphabetical => alphanumeric restore plan (e.g. shardA10 restores to shardB2).
Restoring large sharded clusters can also overwhelm networks where MongoDB Agents are downloading snapshots from Ops Manager(s) at the same time. Please…
8 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
- Don't see your idea?