448 results found

1. Virus threat in MongoDB CLI

   I am facing an issue when downloading MongoDB CLI on my win10 computer. The Windows virus scanner says there is a "Trojan:Win32/Caynamer.A!ml" in the file I am trying to download and ends the download. Is this threat real?

   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

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

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

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

   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

4. Add Azure support for Cloud Manager

   Submitting on behalf of customer - Request to add Cloud Manager support for Azure servers (provisioning, installing an agent, making a custom hostname and doing DNS) and Azure blob for backups. Customer has shared they have had a great experience using Atlas. However due to business requirements, some application stay must on prem. Customer is partnered with Azure and unable to use Cloud Manager for on prem deployments as they cannot use AWS for servers and backups

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

5. Allow MongoDBUser CRD to interact with a MongoDB resource in a seperate namespace

   Allow MongoDBUser CRD to interact with a MongoDB resource in a separate namespace in k8s.

   The goal is to have different teams deploy their resources (including applications, configmaps, secrets, PVCs, MongoDBUser CRDs etc) into their seperate namespaces, but have all of them share a single MongoDB replicaset in a common namespace such as mongodb

   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

6. Include full date/time stamps to OpsManager's logfiles: mms0-startup.log and daemon-startup.log

   Currently records in mms0-startup.log and daemon-startup.log only have time stamp in the format: hour:min:sec,milliseconds.
   eg. 08:28:09,558 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]

   It would be useful to include the full date/time stamps to each record as currently we can't say to which day do the records refer to.

   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

7. Profiler and Performance Advisor without Automation

   Currently it is required to enable automation on a cluster in order use the Profiler/Performance Advisor.

   https://docs.opsmanager.mongodb.com/current/tutorial/profile-database/

   https://docs.opsmanager.mongodb.com/current/tutorial/performance-advisor/

   As automation is sometimes not desired for a cluster, please add the ability to Profile Databases and use Performance Advisor when a cluster is monitored only.

   4 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

8. Ops Manager UI estimates backup time and restore

   Backups and restore estimation as UI feedback for regular and continuous backups

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

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

   Capability to use JWT or SSL certs would be great.

   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

10. Allow multiple authentication sources simultaneously

    Currently Ops Manager authentication supports either the Application Database, LDAP, or SAML, but these methods cannot be combined. Ideally we would like to move to LDAP, but we are stuck with the local authentication method as we depend on a local admin user which is used when first deploying and configuring the Ops Manager ecosystem. We also do not want to depend solely on the availability of the LDAP servers regarding an admin user. The MongoDB cluster deployments do support multiple authentication methods at the same time (we have local admin and monitoring accounts while users are authenticating via LDAP), it would be great if you could allow the same setup for Ops Manager.

    Currently Ops Manager authentication supports either the Application Database, LDAP, or SAML, but these methods cannot be combined. Ideally we would like to move to LDAP, but we are stuck with the local authentication method as we depend on a local admin user which is used when first deploying and configuring the Ops Manager ecosystem. We also do not want to depend solely on the availability of the LDAP servers regarding an admin user. The MongoDB cluster deployments do support multiple authentication methods at the same time (we have local admin and monitoring accounts while users are authenticating via LDAP),… 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

    2 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. Ops Manager to be able to do archiving of Data to a different replica set than you Prod replica set.

    To be able to set up Archiving in Ops Manager so you would be able to keep a certain amount of data in Prod and move the rest of to an Archiving replica set.

    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. Include CPU usage in Sharded Cluster Monitoring Overview

    In the sharded cluster monitoring overview it would be useful to also have the option to display the Process CPU usage to quickly identify shards which have a higher CPU load. Other hardware metrics might be useful as well.

    4 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. Sharding

    When we create a new collection with a shard key using mongosh the same is not reflected in cloud manager. In cloud manager / ops manager the shard key for the new collection is not seen in the shard tab.

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

14. Loadbalance functionality for Ops Manager

    When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
    It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
    Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.

    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

15. Include "Fetch Time" in Profiler timings

    When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

    In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

    Is there a way to configure Profiler to be more realistic, and include the "fetch time" as well as the "query" time?

    Currently, the Profiler seems to be of little us in finding slow queries. We have to find them using other means.

    Thank you.

    When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

    In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

    Is there a way to configure Profiler to be more realistic,… 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

16. Add command for suspending automation

    Add command for suspending automation (similar to what we have for unmanage)

    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  ·  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. OpsManager Application DataBase Backup and Restore

    Ops Manager Application needs a way to backup and restore AppDB without Ops Manager Downtime to recover from infrastructure failures or fatal errors.

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

18. Do not start backups for Sharded clusters unless all requirements are met

    With FCV > 4.2, Backups requires the backup module to be activated on at least one member per shard for sharded clusters but it also doesn't stop one from starting backups if the backup module is activated only on one member of the entire sharded cluster, for example, activating the backup module on a single member of the config server replica set and not on any member of the shards allow for one to start backups.

    Currently, if backups are enabled and at least one of the Replica sets in the Cluster has a backup module, backups will start for the cluster.
    The backups in the "missing" backup agent function scenario would not be consistent.

    With FCV > 4.2, Backups requires the backup module to be activated on at least one member per shard for sharded clusters but it also doesn't stop one from starting backups if the backup module is activated only on one member of the entire sharded cluster, for example, activating the backup module on a single member of the config server replica set and not on any member of the shards allow for one to start backups.

    Currently, if backups are enabled and at least one of the Replica sets in the Cluster has a backup module, backups will start for… 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  ·  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. Improvement of Restore Process in Ops Manager

    Presently Ops manager restore process removes all the data from the target MongoDb deployment and then restores from the user selected Snapshot and subsequently applies the PIT restore.
    
    It is noted that time taken by the restore operations increases as and when the DB size increases. The restore operation would also require the Applications to be shutdown and this would lead to increase in Application downtime during the restore process.

    In order to minimize the downtime we need to reduce the restore time.

    One suggestion to reduce the restore time is to perform automated restore from the latest available snapshots to the standby replica set(Managed by Ops Manager) on regular basis and then perform only the Point In Time Recovery which would only apply the Oplog changes from the latest restored snapshot to the standby replica set and do not delete the data before performing the restore from the target replica set. This would help pointing the applications immediately to the standby replica set after the PIT is completed and minimize the downtime.

    For this the restore operation should have a feature for user to select if the data in the target replica set should be removed or not before performing the PIT restore.

    Scheduling the restore operations from the latest available snapshots on the standby replica set and then performing only the PIT restore from the last available snapshot whenever required without deleting the data from the standby replica set would help restoring the Application data faster.

    Presently Ops manager restore process removes all the data from the target MongoDb deployment and then restores from the user selected Snapshot and subsequently applies the PIT restore.
    
    It is noted that time taken by the restore operations increases as and when the DB size increases. The restore operation would also require the Applications to be shutdown and this would lead to increase in Application downtime during the restore process.

    In order to minimize the downtime we need to reduce the restore time.

    One suggestion to reduce the restore time is to perform automated restore from the latest available snapshots… more

    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

20. Ops Manager global actions (mongocli ops-manager admin)

    Add cli commands in global scope of Ops Manager to allow for scripting actions on all projects (e.g. update all agents after an upgrade of Ops Manager):
    - CRUD projects (prio on get projects to allow for looping over them)
    - CRUD orgs
    - CRUD users
    - global config managemant
    - global alert management

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