Ops Tools
225 results found
-
Only download to /mms/mongodb-releases/ those versions actually in use in a deployment
/mms/mongodb-releases/ is continually updated with the most current minor release of each major version which can fill the partition.
This request is for "Only download to /mms/mongodb-releases/ those versions actually in use in a deployment"
eg if I am only using 4.2.20 in my actual deployments only download the most recent 4.2.x and not 3.6.x
of course if I do decide to deploy a 3.6.x deployment this FR would need to automatically be bypassed and download my 3.6.x and the most recent 3.6.x.
This request is similar to but not the same as another Feature Request:
Do not download EOL…3 votes -
Add to the Continues Backup UI more information about the snapshots
Currently, the Ops Manager UI under Continues Backup only shows the following information about the snapshots:
- Replica set name
- Status
- Last Snapshot
- Last Oplog SliceIt would be very helpful to also see:
- Start date/time
- Finish date/time
- Backup duration
- Snapshot size4 votes -
Support rolling rebuild index
In some particular situation indexes need to be rebuild.
It would be nice to support a rolling index rebuild like Ops Manager does for the standard create index.3 votes -
index review before sharding with OPS Manager
Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
So, several features could exist :
- before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
-…5 votes -
Add compound indexes support for Ops Manager managed Sharding
What is the problem that needs to be solved? Ops Manager Automation does not take into account compound indexes (https://docs.mongodb.com/manual/core/index-compound/), e.g. if we have
{ a: 1, b: 1 }index already exist Ops Manager will still create{ a: 1 }index foraShard Key.Why is it a problem? (the pain) This creates unnecessary indexes with performance impact on the MongoDB Server process.
2 votes -
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 -
connection-pool monitoring
hi
like this, would you please support connection-pool monitoring.regards,
park1 vote -
Allow informational alerts to be sent to PagerDuty
Right now informational alerts can't go to PagerDuty, OpsGenie, or VictorOps. Ideally all alert notifications should go to the same endpoint, even if those alerts are "informational" and no acknowledgement is required.
2 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 -
Create a User in a Single Cluster
When multiple clusters are added into an Ops Manager project, the only way to create a user account is to add it to all of the clusters in the project and to then add server IP Address restrictions to prevent the user from logging into servers other than the intended cluster. This would still create the user account on all of the clusters in the Ops Manager project.
Users would need a way to create a user account on a specific cluster rather than all of the clusters of the project.
2 votes -
Add Timezone support to Ops Manager Application logs
All of our hosts are in the same TZ. We would like to be able to set the Ops Manager related logs timestamps to our local TZ.
10 votes -
There is currently no way to use the UI to search a given hostname at a Global Level within an Ops Manager deployment.
Please provide a feature in OM so we can search globally a given HOSTNAME to know about its related Organization/Replica Set
2 votes -
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 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 -
Option to encrypt mms.https.PEMKeyFilePassword in conf-mms.properties file
Currently, credentialstool only offer encryption for username/password for the AppDB mongo.mongoUri.
It would be great to also have the ability to encrypt the mms.https.PEMKeyFilePassword in conf-mms.properties file, so that is not clear text.
1 vote -
Request Logs - Add timeframe to list of options
While diagnosing historical issues "Request Logs" does not allow for selectable timeframes. As such, for these issues, logs must be manually gathered. Adding an optional timeframe will assist in diagnosing issues much faster.
2 votes -
Project Alert Integration With Rocket.Chat
Integration with Rocket.Chat like done in Slack.
5 votes
- Don't see your idea?