454 results found

1. Allow configuration of alerts (and setting customer alerts) via enterprise operator

   It would be nice to be able to configure an environments alerts directly from the Operator which will be deploying that environment.

   2 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  ·  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

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

   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  ·  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

3. Option to include hidden secondaries in Replica Set Alerts

   As per Replica Set Alerts documentation: "A replica set member is healthy if you run rs.status() for that replica set and the result returns PRIMARY or SECONDARY for that member. Hidden secondaries and arbiters are not counted".

   That is convenient when you take hidden secondaries down for backups but we would like include the hidden members in replica set health monitoring.

   2 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

4. Do not trigger spurious COLLSCAN alerts for getmore commands during watch

   Here's what MongoDB support summarizes about the current behavior: "Upon consulting with the team, they have confirmed that sometimes change streams can trigger collection scans, but these alerts are an artifact of how we calculate the metric today. Unfortunately at the moment, there is no fix for these alerts"

   My suggestion is to fix how the metric is calculated. What is happening in the getmore is not a real COLLSCAN, and it should not be reported (and alerted) as such.

   (Bonus points for including context information in the COLLSCAN threshold alert showing the collection and operation. Just knowing there has been a COLLSCAN against N records is not all that actionable.)

   Here's what MongoDB support summarizes about the current behavior: "Upon consulting with the team, they have confirmed that sometimes change streams can trigger collection scans, but these alerts are an artifact of how we calculate the metric today. Unfortunately at the moment, there is no fix for these alerts"

   My suggestion is to fix how the metric is calculated. What is happening in the getmore is not a real COLLSCAN, and it should not be reported (and alerted) as such.

   (Bonus points for including context information in the COLLSCAN threshold alert showing the collection and operation. Just knowing there has… more

   1 vote

   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  ·  Edit…  ·  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

5. Mongoimport CSV columnsHaveTypes to support ObjectID type

   Mongoimport supports a number of import types via the --columnsHaveTypes switch. It would be great if 'objectid' was added as a type.

   1 vote

   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  ·  Other  ·  Edit…  ·  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

6. Allow create/delete/update custom database role in MongoDB CLI for Ops Manager

   In Altas CLI, the command customDbRoles can be used for create/delete/update custom database role.
   Would it implement in MongoDB CLI for Ops Manger?

   6 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  ·  MongoDB CLI for Cloud Manager and 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

7. mongoimport: trap SIGUSR1 to flush buffer

   If mongoimport is run in the background as a daemon, the user doesn't have many good ways to manually flush the buffer from a scripting standpoint. By default mongoimport flushed data every 1000 documents.

   This feature as already requested at https://jira.mongodb.org/browse/TOOLS-2773 but was closed. I still have the hope that it will be introduced somewhere in future release.

   1 vote

   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  ·  Other  ·  Edit…  ·  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

8. Integrating Ops manager with other enterprise tools

   Increasing foot print and creating a a smooth integration for customer environment for Mongodb by making it ready to plug and play for any enterprise. Big enterprises will have their own backup, monitoring and automation platforms. Mongodb or ops manager must provide options or may have certifies some enterprise backups or monitoring platforms where customers can seamlessly leverage existing features for backup and monitoring instead of building or testing their own things.

   2 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

9. Restore indexes using mongoimport - metadata.json

   When importing an archive from s3 we are given compressed gz files for the JSON data and a metadata.json file which has index info, however there is no efficient way to restore these indexes as mongoimport doesn't support creating indexes. Indexes need to be created manually. When needing to restore multiple collections this can take a very long time.
   It would be great if mongoimport could use this file to create indexes after an import (like mongorestore).

   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

10. Restrict snapshot restore download

    IHAC who would like to be able restrict snapshot restore download links (by IP / opsman role) to prevent anyone with access to opsman server from downloading. They know about the "number of times the restore link can be used" + "restore link expiration" features but would also like this feature. Please contact me for customer details

    2 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

11. Support Cloudian S3 in OpsManager

    OpsManager currently supports the S3 implementations of AWS, IBM Cloud and Dell EMC Elastic Cloud Storage. We would like to use our existing Cloudian S3 storage. We've used it for a while now and it works, but we suggest making this an "officially supported" flavor, too.

    1 vote

    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  ·  Edit…  ·  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

12. In Ops Mgr, provision to create users by deployment rather than by project

    Under a project, Now if a user id created, it gets created in all deployments in the projects. Can we have provision to choose which deployment the user gets created.

    For example, for project A, we have three deployments rs1, rs2 & rs3. Now under security tab, if we add a users, this user get access to all deployment. can we have a choice which all deployment the user exist.

    3 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

13. Release Cadence to allow pegging Minor Version Upgrades prior to GA of next Major Release

    Issue:
    Current requirement to enable 'auto upgrades' to test and take advantage of Minor version updates (Example: 6.x.x >> 6.y.x). As a larger company with a 2-4 week release cycle in our products, we have seen need to start testing a Minor version upgrade to the current Major GA Release (Recent example below).

    Scenario where this could be a problem in summary (See detailed real world story further down):
    - Customer sees a new feature they wish to try.
    - Customer is pegged to last major version upgrade (currently 6.0.x) to allow for pegging the version in production
    - Customer cannot allow for 'auto upgrades' in production due to internal Release Management requirements, and must wait the full year cycle for features added in later minor versions of the current major release.

    The Ask: We respectfully request a resolution to a state where we can choose to peg any of our clusters to a specific minor version (i.e. 6.1.x, or 6.2.x...) and allow only auto upgrades in the patch/bug release numbers rolled out by Atlas. Thank you for your time and response to this critical upgrade in scheduling & control over Minor version upgrades.

    More detailed summary of need for control over Minor Release Update Cycles/Scheduling:
    As we have our own release management requirements, any change to a Production environment must go through UAT and Performance testing and approval before the release. Currently, with requirement of enabling 'auto upgrades' to move up to available Minor Release, we are hamstrung until late in the Major release cycle to begin testing and releasing a minor version in lower environments to then implement in Production. this is due to our internal Release Management requirement to peg the MongoDB version and driver in Production to a fully tested release, and to have lower environments testing and validating on same IaaS release version as production. And pegging a version is only allowed at the Major version going to GA. We wish to ask that Minor versions be left to live for 12-15 months to allow for pegging a minor version upgrade during the year. This would allow our teams to implement a Minor version upgrade early... and peg to that version pending the annual GA release to come.

    Below I highlight the real world example that caught our team in a catch-22 with v5.0 not meeting requirements of our application in sharded configuration, requiring us to enable 'auto upgrades' to get to 5.1.x or later.

    Resulting Request:
    We would like the ability to peg our clusters to specific minor releases. Example: to 5.3.x where patch releases are acceptable, but minor version updates to 5.4.x are not allowed until we have tested and approve within same our own CICD pipeline and process.
    Allowing for 'auto upgrades' in our clusters based on Atlas rollout schedules poses unwarranted risk to the production assets of the End Users
    The ability to be alerted of available minor updates with option to choose when to begin our own test/release and schedule same is requested.

    Recent situation/scenario:
    With requirement for 'auto updates' we were in a catch-22 with 5.0.x And 5.3.x, where we needed the features of graph lookup with sharded configuration in production.
    - We are rapidly reaching critical resource issues in Production with a Primary/Replica configuration.
    - We must proceed with upgrade to Sharded configuration to 1) allow for horizontal scaling to relieve pressure on Primary nodes for Read Preference Primary for mission critical operations requiring high idempotency, and that do not allow for eventual consistency within the SLAs and 2) relieve pressure on Oplogs due to high throughput and rapid data changes during normal operations. We have operations that lead to a requirement on a primary/replica set to be now 1.2TB to prevent OpLog window from dropping below 12hrs. - With horizontal scaling, we can spread the load on read primary across multiple nodes, which will alleviate the need for such a large Oplog Size, leading to better management and availability of storage.
    Without the 5.3.2 upgrade and change in our current primary/replica >> sharded configuration. We could not proceed with the much needed upgrades without accepting release management risks associated with enabling 'auto upgrades'. Although the recent scenario is resolved as 6.0 is now GA, if this were earlier in the GA release cycle, we would either 1) be blocked from the above critical upgrades, or 2) Forced to accept the risks of an 'auto upgrade' being implemented in Production ahead of our NonProd clusters. Going against best practices for Release Management.

    Issue:
    Current requirement to enable 'auto upgrades' to test and take advantage of Minor version updates (Example: 6.x.x >> 6.y.x). As a larger company with a 2-4 week release cycle in our products, we have seen need to start testing a Minor version upgrade to the current Major GA Release (Recent example below).

    Scenario where this could be a problem in summary (See detailed real world story further down):
    - Customer sees a new feature they wish to try.
    - Customer is pegged to last major version upgrade (currently 6.0.x) to allow for pegging the version in production
    - Customer… more

    1 vote

    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  ·  Other  ·  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

14. MongoDB Tools Apple Silicon native version

    6.0 now has a native release for Apple Silicon, but the tools are still compiled for x86_64. The https://github.com/mongodb/mongo-tools/blob/master/PLATFORMSUPPORT.md seems to point towards new platform support on internal systems like https://evergreen.mongodb.com/distros - can we get a native build of the tools ?

    1 vote

    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  ·  Other  ·  Edit…  ·  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

15. Add cluster_id parameter in host detail API

    As per the link https://www.mongodb.com/docs/ops-manager/current/reference/api/measures/get-host-process-system-measurements/ and below API :

    curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest
    --header "Accept: application/json"
    --include
    --request GET "https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0/groups/{PROJECT-ID}/hosts/{HOST-ID}/measurements?granularity={TIME-INCREMENT}&period={PERIOD}}&pretty=true"

    This will give us the details pertaining to one host and one project. However what if one host has multiple processes and part of multiple replica sets within same project in OPS Manager? Then it becomes difficult to gather gather data. Hence a clusterid parameter should also be added to distinguish details based on host pertaining to which cluster or replica set along with projectid which is already present.

    1 vote

    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  ·  Automation  ·  Edit…  ·  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

16. Migration Guide for OpsManager to enterprise-operator

    It would be great to have a migration guide or documentation to help with migrating an existing OpsManager installation to the kubernetes enterprise-operator based installation.

    2 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  ·  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

17. Export Reports and Graphs

    OPtions to export the reports and graphs into a PDF or office tool will help Incident Management process to a great extend.

    1 vote

    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  ·  Edit…  ·  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

18. rename action for backup daemon "delete daemon" to "deactivate daemon"

    when you press link "delete daemon" on Admin->Backup->Daemons page it "deletes" daemon from this page, but after mongodb-mms.service gets restarted, this daemon comes up again. this link does not delete daemon - it actually deactivate backup daemon. another part for deactivation of daemon is to modify settings for service mongodb-mms to start only mms application without daemon.

    1 vote

    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  ·  Edit…  ·  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

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

    5 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

20. mongocli - changing server type

    There is a missing option to change server type via mongocli. You can list the server type for the project, but not change it.

    available option for list:
    mongocli om serverUsage projects hosts list --endDate 2020-01-01 --startDate 2021-01-01

    https://www.mongodb.com/docs/mongocli/v1.8/reference/ops-manager/server-usage-list-all-project-hosts/

    1 vote

    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  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Edit…  ·  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