487 results found

1. trigger a queryable Backup Snapshot restore via Ops Manager public API

   We would like to periodically provision queryable snapshots on a programmatic basis (aka Ops Manager public API call) to easily get a consistent dump of sharded clusters in order to put those dumps in a "very safe location". We want to use this as part of a last resort backup strategy. The idea is that a dump is much easier to be restored by a "last resort restore app" compared to the http-downloaded plain data files.

   One other option to extract the contents of a sharded cluster would be to use "Long Running Queries" but this cannot be used along with mongodump.

   We would like to periodically provision queryable snapshots on a programmatic basis (aka Ops Manager public API call) to easily get a consistent dump of sharded clusters in order to put those dumps in a "very safe location". We want to use this as part of a last resort backup strategy. The idea is that a dump is much easier to be restored by a "last resort restore app" compared to the http-downloaded plain data files.

   One other option to extract the contents of a sharded cluster would be to use "Long Running Queries" but this cannot be used along… more

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Alerts: Webhook integration authentication with basic auth

   In secure environments, it is required that webhook endpoints are secured with basic authentication at a minimum. Currently, Webhook alerts only provides an HMAC-SHA-1 signature.

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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
   etc

   There is no way to get this data into Prometheus at the moment

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. 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 consider providing a mechanism to throttle the number of Agents concurrently downloading snapshots with the understanding that this will come at a cost of longer restore times. This is helpful for large restores scheduled on a regular basis with expected downtime of a QA or UAT environment where uptime is not a priority.

   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… more

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Configure MongoDB Automation Agent collecting stats on some collection to not trigger alerts

   We just had a support case about some alerts being raised on our cluster because the MongoDB Automation Agent collecting stats on some collection doing queries without index triggers "Scanned Objects / Returned" ratio has went over 1000.

   It would be really nice to at least not raise alerts when it's the mongodb automation agent that triggered it. Were monitoring our alerts a lot and these are false positive we can't do anything about it seems other than create all the indexes it needs, which might change over time. We have no guarantee of which index it needs.

   Another alternative would be to tell us in the performance advisor which index to create to avoid those.

   I'm not sure what's the right solution here, but the way this works right now is wrong.

   We just had a support case about some alerts being raised on our cluster because the MongoDB Automation Agent collecting stats on some collection doing queries without index triggers "Scanned Objects / Returned" ratio has went over 1000.

   It would be really nice to at least not raise alerts when it's the mongodb automation agent that triggered it. Were monitoring our alerts a lot and these are false positive we can't do anything about it seems other than create all the indexes it needs, which might change over time. We have no guarantee of which index it needs.

   Another alternative… more

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Allow customization of Alert's Subject/Body

   Currently alerts do not allow for any customization of the Subject or Body. It would be useful to allow customization of both the Subject and Body of emails and other alert methods. This would allow customers to add information, such as links to internal runbooks or documentation, to assist with resolving the alert.

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Introduce Helm Chart for MongoDB, MongoDBUser and secrets

   Provide a helm chart that deploys MongoDB, MongoDBUser, secrets and all other resources needed.

   The goal is to simplify the deployment of a MongoDB instance and everything that comes with it down to a helm one-liner.

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  Andrey responded

   We have an example of a HELM chart that can deploy all resources.
   We will be working on adding more refined charts
   https://github.com/mongodb/mongodb-enterprise-kubernetes/tree/master/helm_chart

9. Allow conditions for all alerts based on DB/cluster name

   We have a need to route alerts based on our database/cluster's impacted instead of having them apply to any in the current project. I know some of them can condition based on host name, which uses the cluster name, but most alert types have no similar option.

   Examples would be:
   Search Index Build Complete
   Search Index Build Failed

   These are sent without conditions and even the message does not indicate what cluster they are for (although you can guess based on the collection name provided).

   We do not have the option to route these ourselves with a webhook, as the relevant information is not provided there either.

   We have a need to route alerts based on our database/cluster's impacted instead of having them apply to any in the current project. I know some of them can condition based on host name, which uses the cluster name, but most alert types have no similar option.

   Examples would be:
   Search Index Build Complete
   Search Index Build Failed

   These are sent without conditions and even the message does not indicate what cluster they are for (although you can guess based on the collection name provided).

   We do not have the option to route these ourselves with a webhook, as the… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Monitoring / Alerts  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add addition authentication mechanisms to the Ops Manager Alerting webhook

    Capability to use JWT or SSL certs would be great.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Consider supporting the installation of mongosh via Ops Manager/automation agent

    Today, it is possible to install MongoDB software (mongoimport/export, mongodump/restore, mongo, bi connector) from Ops Manager via the automation agent.

    Ideally, it will be possible to have the same experience for the new MongoDB Shell (mongosh), so that customers don't need to put in place a separate set of processes nd scripts to install it.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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 Slice

    It would be very helpful to also see:
    - Start date/time
    - Finish date/time
    - Backup duration
    - Snapshot size

    •  

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. arm64 support for Cloud Manager Agent

    We would like to install Cloud Manager Agent on arm64 based linux machines.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Cloud Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add collection level statistics to the measurements API

    Get Database Measurements currently provides information from dbStats.

    Adding collection level statistics would be useful for gathering information via the API on a regular basis to measure growth of each collection and other metrics. Data Explorer functionality is not available via the API.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Ability to customize subject line for System & Global Alerts

    Currently there's no way to customize the subject line of either a system or global alert. The subject line only has the project name & time. It doesn't even say why the alert was generated until the email alert is opened. Having the ability to modify the subject line, even if it's to certain predefined fields such as alert condition for example would be helpful in addressing alerts in an efficient and effective manner.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add `serverStatus.uptime` counter info into Metrics

    What is the problem that needs to be solved? We already collect serverStatus.uptime counter info from each and every MongoDB Server process, so we just need to add serverStatus.uptime counter info into Metrics so that it will be possible to track serverStatus.uptime changes through the time.

    Why is it a problem? (the pain) If you'd like to calculate MongoDB Server process availability to know for how long your MongoDB Server process(es) was/were up and running, you'll need to analyze MongoDB Server process logs (in case if they are ever available for required period of time) to see last time MongoDB Server process was stopped/started. With serverStatus.uptime counter info available in Metrics at Ops Manager side it will be very easy (also programmatically via Public API call) to identify down time of MongoDB Server process since serverStatus.uptime counter will be reset every time MongoDB Server process is restarted (i.e. a MongoDB Server process restart will always be indicated easily).

    What is the problem that needs to be solved? We already collect serverStatus.uptime counter info from each and every MongoDB Server process, so we just need to add serverStatus.uptime counter info into Metrics so that it will be possible to track serverStatus.uptime changes through the time.

    Why is it a problem? (the pain) If you'd like to calculate MongoDB Server process availability to know for how long your MongoDB Server process(es) was/were up and running, you'll need to analyze MongoDB Server process logs (in case if they are ever available for required period of time) to see last time MongoDB… more

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add Kerberos Auth to MongoDBUser CR
    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Identify the snapshot of each project and its size in S3 blockstore

    Calculating the storage size consumed by snapshots for each projects deployments for the storage size consumed individually in S3 Blockstore. However, on the S3 snapshot store the data will be stored in the below format which doesn't include any project id to identify the specific project.
    s3://bucket_name/0E3AA1971D5CF1CA52F9AF22A4228F10293AE9804D43FBF7EB5DDE38DB06B74A/5b27b0e4083826088f259f28_A s3://bucket_name/1860B12165FB7ED336DDAB9D306EF38E18FCBD36BF695904C497B825F83581DC/5b27b0e4083826088f259f28_A

    This feature is helpful for the customers to understand and segregate the storage consumption by each deployments

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Supporting the installation of mongosh in Ops Manager Local Mode

    Ops Manager v6.0+ supports installing the new mongo shell (mongosh) to the deployment nodes. This feature is not supported in Ops Manager Local Mode.

    It would be convenient to the Ops Manager Automation user if they could upload the mongosh binary to the Ops Manager Versions Directory and Ops Manager will install the binary to the deployment nodes similar to the MongoDB Binary and MongoDB Database Tools.

    Currently, the customer with Local Mode needs to manage the installation of mongosh outside of Ops Manager Automation.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating