Skip to content

Ops Tools

← MongoDB Feedback Engine

How can we improve the Operational Tooling MongoDB provides?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

479 results found

  1. 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
    0 comments  ·  Automation  ·  Admin →
    How important is this to you?

  2. 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
    0 comments  ·  Automation  ·  Admin →
    How important is this to you?

  3. 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
    1 comment  ·  Ops Manager  ·  Admin →
    How important is this to you?

  4. 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
    1 comment  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  5. 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
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  6. 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 mongod log 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
    0 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  7. 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 mongod and mongos log 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 mongod log 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 the mongod…

    4 votes
    0 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  8. 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
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  9. 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.png flow diagram has been attached to this Feature Request…

    4 votes
    1 comment  ·  Ops Manager  ·  Admin →
    How important is this to you?

  10. 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
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  11. 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
    1 comment  ·  Ops Manager  ·  Admin →
    How important is this to you?

  12. Single Project Programmatic API Keys should not require Org User Admin role for IP Whitelists update

    When setting a Programmatic API Key in the MongoDB Ops Manager for a given Project, it seems Project Owners are unable after setting the Key to update the IP Whitelist as they require Organization User Admin role to perform such action (screenshot attached).

    I guess this makes sense if the same Programmatic API Key is shared between multiple Projects inside the same Organization, but not really if this is applied only to one single Project (i.e. Project Owners should be able to amend the IP Whitelisting of their own API Keys).

    I wonder if this could be enhanced in further…

    4 votes
    1 comment  ·  Ops Manager  ·  Admin →
    How important is this to you?

  13. To offer a terraform provider for self-manage MongoDB environment

    4 votes
    1 comment  ·  Automation  ·  Admin →
    How important is this to you?

  14. Federate different Ops Manager instances

    When multiple Ops Managers are running across multiple environments it is difficult see the overall picture.
    A a federated dashboard that can provide a view into different environments, see overall list of clusters and some basic information about them.

    4 votes
    2 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  15. Add specific label to Arbiter deployment to distinguish it label-wise

    As per https://github.com/mongodb/mongodb-kubernetes-operator/issues/1442 we would like to request to either and/or:

    a) have the operator add a new label to replica and arbiter statefulset deployments to distinguish them from each other
    b) have the ability to add your own labels to specifically the replica OR the arbiter statefulset deployments

    Having the ability to easily filter arbiter statefulsets from non-arbiter statefulsets would be great. This is useful for example for backup tools that run commands on pods based on a combination of labels, to exclude any arbiters from backup.

    3 votes
    1 comment  ·  Community Kubernetes Operator  ·  Admin →
    How important is this to you?

  16. Change the "Replica set has a late snapshot" Alert from Global to Project level

    Currently the "Replica set has a late snapshot" Alert is a Global Alert. It would be useful to have this changed to a Project level Alert so that the Alert can be tuned for each specific deployment to provide better customization of the Alert.

    3 votes
    0 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  17. Documentation: API equivalents for each action on OpsManager

    In the documentation, for each action on OpsManager it should be explained how to achieve the same result using the OpsManager API (or an equivalent mongocli command, if it exists).
    For example, in the pages describing how to configure Backup stores in the OpsManager UI, it should also be explained which APIs to use (admin/backup).

    3 votes
    0 comments  ·  Automation  ·  Admin →
    How important is this to you?

  18. Ops Manager API should be authenticated via Certificate

    Ops Manager API uses HTTP Digest Authentication, this method requires a username and a password which are hashed and provided in the form of registered Ops Manager account, and the password which is a Public API Key associated with that account.

    But as part of security feature we should be allowed to use Authentication based on SSL certificates as we are using for Client connection, This will help to secure the self automation process if we are developing any internally.

    3 votes
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  19. Export Cloud Backup to AWS S3 as CPS

    Currently, the Atlas provides possibility to configure an automated export cloud backups to an AWS S3. It uploads the contents of your database to S3 as gzip files with documents in extended JSON format within. It is possible to restore from these files using mongoimport tool.

    However, for some our use cases we would like to have backups exported to our AWS S3 as CPS (cloud provider snapshots) - actually a snapshot of the database directory at the filesystem level - in order to be able to restore very fast (the import via mongoimport and re-building of indexes can take…

    3 votes
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  20. Allow the services port name prefix customization in Enterprise Kubernetes Operator to support Istio Sidecar requisites

    Istio Sidecar requires services port name prefix with a protocol name, but the services port names created by the Enterprise Kubernetes Operator are not customizable (e.g.)

    • operator-webhook
    • ops-manager-backup-daemon-svc
    • ops-manager-db-svc
    • ops-manager-svc

    It may be possible to allow the customization of these names?

    3 votes
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
1 2 … 6 8 10 … 23 24
  • Don't see your idea?

Ops Tools

Categories

Feedback and Knowledge Base

(thinking…)