Ops Tools
469 results found
-
Alerts if MMS Application goes down
Dear Team,
We are looking for an option to set alerts if any of the Ops Manager Application goes down in a HA environment. Being with HA configuration, we at least expect this feature to in place - as currently it looks like that OPS Manager is not aware of its own HA configuration.
Mongo Case: 00723232
Thanks,
Tom1 vote -
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 -
Create a litmus chaos to test mongodb in containers
To support chaos engineering.
1 vote -
MongoCLI Wizard Flag
Currently a user needs to manually insert at least all the required flags to use a mongocli command. We can implement the flag --wizard which guides the user through flags with interactive prompts.
This flag should be added to all the commands to allow the user to get interactive prompts when required flags are not provided.The wizard flag will have the following functionalities:
- Asking to the user the required flags with interactive prompts
- Showing a list of optional flags and asking to insert their values if selected
- In case of describe commands, showing the list of resources available (mongocli…
1 vote -
Ability to turn on/off MongoDB Agent auto-update in specific/all Cloud Manager/Atlas Project(s)
What is the problem that needs to be solved? Ability to turn on/off MongoDB Agent auto-update in specific/all Cloud Manager/Atlas Project(s).
Why is it a problem? (the pain) Cloud Manager/Atlas Project will warn a user with One or more software components are out of date: MongoDB Agent every time a new version of MongoDB Agent is released, so a user will need to always manually click on
Update Software Componentsbutton to get rid of that warning (filename: 2020-04-06mongodbagentupdatewarning.png). Frequent updates of MongoDB Agent creates lots of noise for users who is willing to get rid…7 votes -
Add hostname/port attributes into all Cluster/Replica Set alert types
What is the problem that needs to be solved? Add hostname/port attributes into all Cluster/Replica Set alert types generated via SNMP Alert Traps, Ops Manager's Public API calls (Project/Global Alerts) and Alert Webhooks (Project/Global Alerts).
Why is it a problem? (the pain) Hostname/port attributes are currently missed in Cluster/Replica Set alert types and we only provide a name of the Cluster/Replica Set for which the alert was generated. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see hostname/port information of a Shard/Replica Set for which such alert was generated, in order to quickly understand…
7 votes -
Make snapshot retention policy more customisable
Make the retention policy of Ops Manager snapshots customisable so we can choose custom values (like 21) to be more flexible with the settings.
12 votes -
mongoimport should assume json with arrays
When running something like "mongoimport --host Cluster0-shard-0/cluster0-shard-00-00-MY.mongodb.net:27017,cluster0-shard-00-01-MY.mongodb.net:27017,cluster0-shard-00-02-MY.mongodb.net:27017 --ssl --username MYUSER --password MYPASS --authenticationDatabase admin --db db --collection coll --type json --file D:\downloads\records.json". You get error "2019-09-28T15:40:34.076-0600 Failed: cannot decode array into a D". You have to use the "--jsonArray". Why wouldn't this be the default. Almost all JSON objects have arrays via mass import/export. Worse case, it should give a better error message.
1 vote -
Significantly Throttle or Skip MongoDB Agent Connections to Intentionally Disabled Clusters
When performing an automated snapshot restore in Ops Manager, the MongoDB Agents shut down all MongoDB cluster members while the snapshot(s) are downloaded to the dbPath's.
During this phase of the plan, the MongoDB Agents continue to attempt network connections to the cluster members; as frequently as ~4 per second per mongod. This traffic may pose problems for certain cluster deployment designs. Of note, clusters that are "micro-sharded" (multiple cluster members residing on the same physical hosts) and clusters with members in a remote datacenter can receive an amplification and/or excessive amount of connections relative to what the network can…1 vote -
In Ops Manager, the user show as all deployment. How can i change from 'all deployment' to a specific deployment.
In Ops Manager, the user show as all deployment. Using MMS, How can i change from 'all deployment' to a specific deployment.
MongoDB User Name MongoDB Roles Deployment
yyyyy xxxx-rw@xxxx all deployments1 vote -
Allow additional port for SMTP configuration
Our Cyber team doesn't want SNMP traffic on default port, need dev team's help to enable additional (or custom) ports to be setup in SMTP configuration (e.g. port 163).
1 vote -
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 -
Mark IP ranges when user add to whitelist more than 4 address network
Security/Network Access/IP Access List
When adding the ip range it is easy to make mistake an example instead of 192.168.5.5/32 add 192.168.5.5/3
It will be great to mark as read or ask user "are you sure to add range with mask <30"
1 vote -
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 -
integration with Mattermost for notifications
It would be good to replicate the integration with Slack but using Mattermost. Mattermost is open source and allows the companies to deploy their own messaging server. Some organizations are moving from Slack to Mattermost for this reason.
2 votes -
Filter/Sort Process List View
In previous versions of Ops Manager, you could filter the process list page. It would be nice to bring that back, so we could quickly identify processes which do not have recent pings, etc.
3 votes -
adminCredentials secret should always be source of truth for OpsManager
The secret is only taken into account by OpsManager initially when OpsManager is deployed. As soon as the password of this user is changed in OpsManager, this secret is out of sync.
From the docs: "Use these credentials to log in to Ops Manager for the first time. Once Ops Manager is deployed, you should change the password or remove this secret."
https://docs.mongodb.com/kubernetes-operator/v1.4/tutorial/plan-om-resource/#prerequisitesOption 1: This secret should be in-sync with the OpsManager database. Preferably the sync should be from the k8s secret to the OpsManager database.
Option 2: Create a CRD "MongoDBOpsManagerUser" that handles User/Password management for OpsManager similar…
6 votes -
Periodically notify users of unused versions located in versions directory
As a safety measure for admins in Ops Manager to avoid facing issues due to unnecessary disk occupation under the Ops Manager installation directory:
Send periodic notifications (configurable) i.e: once a month; to notify what binaries are not being used by none of the components in their environment so they can evaluate to delete them in order to free up space on their Ops Manager servers.
5 votes -
Collect hardware metrics even if there's no managed mongo process
Collect hardware metrics even if there's no managed mongo process
Have Automation Agent collect hardware metrics on unmanaged mongo hosts.
Automation agents doesn't collect hardware metrics unless there's a managed mongo process. This means we can't provide centralized system monitoring for a heterogeneous environment, where some clusters are running on their own and others are under automation, or on any non-managed host.
8 votes -
To setup number of backup daemons in ops-manager.yaml
In ops-manager.yaml, can we define the number of the initial backup daemons?
5 votes
- Don't see your idea?