448 results found

1. Support for cPanel

   Cpanel doesn't have any support for Mongodb

   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

2. Use word, not letter to define log levels in Ops Manager

   The following log messages are "info" level messages which can be found in the kubernetes logs from the ops-manager-db pods:

   {"logType":"mongodb","contents":"2020-12-16T02:42:28.557+0000 I  WRITE    [conn7329] update monitoringstatus.config.agentSessions command: { q: { _id: \"mongodb-rs-1.mongodb-rs-svc.mongodb.svc.cluster.local-48cc126fc451d9fa2ffa7569363971f2-5fbedc8dc354771c77dd1932\", s: \"KHNA9JiqXcos5V0d\" }, u: { $set: { s: \"PRIMARY\", p: true } }, multi: false, upsert: false } planSummary: IXSCAN { _id: 1 } numYields:0 queryHash:6C451E2F planCacheKey:38AD5486 ok:0 errMsg:\"E11000 duplicate key error collection: monitoringstatus.config.agentSessions index: cid_1_s_1 dup key: { cid: ObjectId('5fbedc8dc354771c77dd1932'), s: \\\"PRIMARY\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } }, Mutex: { acquireCount: { r: 1 } } } flowControl:{ acquireCount: 1 } storage:{} 200ms"}
   
   {"logType":"mongodb","contents":"2020-12-16T02:42:53.558+0000 I  WRITE    [conn129189] update backupagentstatus.backupAgentSessions command: { q: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \"unassigned\", $or: [ { sessionKey: \"5fd130ec9621b221acd18451\" }, { heartbeat: { $lt: 1608086273347 } } ] }, u: { $set: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \"unassigned\", sessionKey: \"5fd130ec9621b221acd18451\", heartbeat: 1608086573347, hostname: \"mongodb-rs-0.mongodb-rs-svc.mongodb.svc.cluster.local\", addr: \"10.200.30.0\" }, $inc: { callsSinceSuccess: 1 } }, multi: false, upsert: true } planSummary: IXSCAN { groupId: 1, tag: 1 } keysInserted:1 numYields:0 queryHash:5BA6C0B5 planCacheKey:AEFF88E2 ok:0 errMsg:\"E11000 duplicate key error collection: backupagentstatus.backupAgentSessions index: groupId_1_tag_1 dup key: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \\\"unassigned\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } }, Mutex: { acquireCount: { r: 1 } } } flowControl:{ acquireCount: 1 } storage:{} 209ms"}
   

   Despite the fact that the word "error" is in these logs many times, and they have an error code, error name, and error message, this is considered an info level log.

   This is because the letter I is after the date. This makes using regex really hard when trying to setup alerts and monitoring, if I wanted to exclude info level logs.

   It would be great of instead of using a letter like I, W, or E, a word or abbreviation was used such as INFO, WARN or ERROR.

   The following log messages are "info" level messages which can be found in the kubernetes logs from the ops-manager-db pods:

   {"logType":"mongodb","contents":"2020-12-16T02:42:28.557+0000 I  WRITE    [conn7329] update monitoringstatus.config.agentSessions command: { q: { _id: \"mongodb-rs-1.mongodb-rs-svc.mongodb.svc.cluster.local-48cc126fc451d9fa2ffa7569363971f2-5fbedc8dc354771c77dd1932\", s: \"KHNA9JiqXcos5V0d\" }, u: { $set: { s: \"PRIMARY\", p: true } }, multi: false, upsert: false } planSummary: IXSCAN { _id: 1 } numYields:0 queryHash:6C451E2F planCacheKey:38AD5486 ok:0 errMsg:\"E11000 duplicate key error collection: monitoringstatus.config.agentSessions index: cid_1_s_1 dup key: { cid: ObjectId('5fbedc8dc354771c77dd1932'), s: \\\"PRIMARY\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w:

   … 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

3. Rewrite Informational Message "E11000 duplicate key error collection"

   Rewrite the informational AppDB log message so that monitoring tools such as Dynatrace and Splunk does not consider this message as an error message.

   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  ·  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 ability to merge metrics when host renamed

   If a host is renamed and a new mapping is made with a unique ID, there is no way to merge the metrics to view the, historically.

   Adding the ability to merge metrics from previous hosts (when the user is sure the hosts are equivalent) would allow history to be viewed and maintained.

   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  ·  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. Ability to control Ops Manager log rotation from an Admin Page in the UI

   The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

   Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

   Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

   Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses to configure Ops Manager logs and log rotation for /opt/mongodb/mms/logs/mms0.log and /opt/mongodb/mms/logs/daemon.log. By default this is configured with the following settings:

   
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${log_path}.log</file>
<encoder class="com.xgen.svc.mms.util.HeaderPatternLayoutEncoder$Classic">
<pattern>
%d{"yyyy-MM-dd'T'HH:mm:ss.SSSZ"} [%thread] %XF{groupId, "gid:%s "}%XF{jobId, "jobId:%s "}%-5level %logger [%file.%method:%line] - %msg%n
</pattern>
</encoder>
<!-- Rollover the logs once per day, keep 30 days, compressed -->
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${log_path}.%d{yyyyMMdd}.log.gz</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
</appender>


   The file /opt/mongodb/mms/conf/logback-access.xml controls rotation of the /opt/mongodb/mms/logs/mms0-access.log. It has the same <!-- Rollover the logs once per day, keep 30 days, compressed --> policy.

   The logs will be compressed and rotated each day and deleted after 30 rolling days. If you modify the maxHistory option to 10, this should delete the files after 10 days. Please note that any upgrade of Ops Manager may overwrite this change with a new configuration file. Additionally, after modifying these values you will need to restart Ops Manager.

   The /opt/mongodb/mms/logs/mms-migration.log, mms0-startup.log and daemon-startup.log log files are not rotated as it contains only some log entries generated during the startup/migration phases of the Ops Manager Application Server processes.

   The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

   Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

   Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

   Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses… 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

   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

6. bigpanda

   Prefer to get BigPanda integrated with OpsManager for event correlation .
   www.bigpanda.io

   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

7. Support ClusterAuthMode X509

   Customer is trying to deploy a RS with X509 internal auth. The missing RS parameter clusterAuthMode: X509 can be set via GUI but not via CLI.

   Customer would appreciate full support for this mode using the CLI.

   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

8. 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,
   Tom

   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

9. Create a litmus chaos to test mongodb in containers

   To support chaos engineering.

   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

10. 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 atlas cluster describe, list the available clusters)
    • Letting users select a specific value from a list of accepted values
    • If no required flags are given, mongocli will start the wizard mode

    GitHub PR: https://github.com/mongodb/mongocli/pull/511

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

    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

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

    This feature request is to make the MongoDB Agents state aware. If the agent plans call for shutting down the cluster members, skip or avoid frequent network connectivity tests until the download of the snapshot(s) completes.

    This enhancement will also have the benefit of reducing spurious error logging during cluster maintenance and restore from backup.

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

13. 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 deployments

    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

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

    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

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

    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

16. cert-manager & external-dns integration

    Since the kube CA integration is deprecated, the operator should have an option to integrate with cert-manager and external-dns for automatic tls and dns records.

    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  ·  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
    under review  ·  AdminDan (Admin, MongoDB) responded

    Cert manager is already possible using the Operator, we have a guide here.

    
    

    External DNS is not something we currently integrate, though it's under consideration.

17. It would be perfect, If I have "Credential ID" and "Verification Link" for courses that I have completed. Yes, I know, MongoDB provides t

    It would be perfect,

    If I have "Credential ID" and "Verification Link" for courses that I have completed.

    Yes, I know, MongoDB provides this information for professional certified developer, but

    Why not for the certificate of completion?

    •  

    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

18. Ability to set snapshotRetentionDays value to 1

    Need to be able to retain 1 day backups only or just daily backups. Need to reduce 3 day worth of archive.

    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. alert when one or more monitoring agents in a project fail (not only when there are no agents left)

    alert when one or more monitoring agents in a project fail (not only when there are no agents left)

    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  ·  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. move/copy pagination buttons on top of log screen

    when you browse agent logs( automation/monitoring/backup), the size of records is different because some records can take more than 1 line.
    as a result pagination buttons < and > at the bottom of the screen have different location on every page -so it's hard and frustrating to find new location of buttons - particularly when you need go through 10-50 pages...

    but the top of the page is always is on the same place.
    it would be nice to implement one of 3 options :
    1. add keyboard shortcut to go forth and back between pages
    2. duplicate pagination buttons < and > at the top of the page - so they will always be in the same location
    3. modify output of each screen so it will have fixed height so buttons at the bottom will always be at the same location.

    when you browse agent logs( automation/monitoring/backup), the size of records is different because some records can take more than 1 line.
    as a result pagination buttons < and > at the bottom of the screen have different location on every page -so it's hard and frustrating to find new location of buttons - particularly when you need go through 10-50 pages...

    but the top of the page is always is on the same place.
    it would be nice to implement one of 3 options :
    1. add keyboard shortcut to go forth and back between pages
    2. duplicate pagination buttons… 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