Ops Tools
448 results found
-
Display the feature compatibility version (FCV) in Cloud Manager/Ops Manager UI
The FCV could be different than the MongoDB version. Also, sometime the FCV on different shards/CSRS in a sharded cluster might be different (e.g. FCV is upgraded on the shards, but for some reason FCV is not upgraded on the CSRS), and this could cause issues.
It would be nice if FCV is displayed next to the MongoDB version information. So that we can spot out the discrepancy quickly.
1 vote -
Enable S3 Snapshot Storage via Kubernetes Operator with IAM role
Configuring an S3 Snapshot Storage with IAM roles is only possible via Ops Manager UI or API.
It would be great to be able to do this configuration via the MongoDB Kubernetes Operator.
1 vote -
Allow Ops manager to downgrade FCV
Ops Manager UI (4.0 -4.4) does not allow downgrading of Feature Compatibility Version (FCV), once the FVC has been upgraded to a higher version. Ops Manager automatically
removes the lower version from the supported FCVs once upgrade completes. But the cluster deployment allows downgrading one level using shell commands. This limitation makes it difficult when planning an upgrade as regression process are more difficult.
We are in the process of upgrading the environment from 4.0 to 4.4 (which requires an intermediate upgrade to 4.2.). So the downgrade process is so difficult with Ops Manager UI.1 vote -
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 -
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 -
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 -
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 -
Add ability to have systemLog redirected to stdout (just have to remove systemLog.destination and path)
To be able to have MongoDB logs redirect to stdout and this having it into GKE CloudLogs, we should NOT configure a systemLog.destination nor a systemLog.path.
In 0.6.0 release, systemLog.destination and path are hardcoded and cannot be nullable.
see automationconfigbuilder.go at line 208:
...
process.SetSystemLog(SystemLog{
Destination: "file",
Path: path.Join(DefaultAgentLogPath, "/mongodb.log"),
})
...1 vote -
S3 Snapshot Store Speed Test
It is often quite difficult to diagnose latency/bandwidth/generally slow S3 storage. It would be useful if Ops Manager could run a short test to show:
- How fast a single large object can be PUT and GET
- Measure parallel PUTs and GETs against test objects
- How much latency there is between Ops Manager and S3
1 vote -
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 -
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 -
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 -
I want to auto scale vertically and horizontally nodes cpu or disk in Ops Manager
As a DBA using Ops Manager, I want to auto scale vertically and horizontally nodes cpu or disk when certain thresholds are met. As of right now, there is no auto scale functionality in Ops Manager.
1 vote -
I want control the timing of when that rollout happens on Ops Manager
As a DBA using Ops Manager, when I rollout a cluster or project level change, I want control the timing of when that rollout happens so that I can notify the end users of when an change may occur. As of right now, those changes happen immediately all the entire cluster/project and may create a non-scheduled outage.
1 vote -
Able to move a database from one MongoDB cluster to another MongoDB cluster
As a DBA using Ops Manager, I want to be able to move a database from one MongoDB cluster to another MongoDB cluster so I can consolidate databases into a single cluster. As of right now there are no consolidation tools within Ops Manager.
1 vote
- Don't see your idea?