Docs Menu

Docs HomeMongoDB Ops Manager

MongoDB Agent Changelog

On this page

Released with Ops Manager 6.0.22 on 2023-01-04.

Released with Ops Manager 6.0.21 on 2023-12-14.

Released with Ops Manager 6.0.20 on 2023-11-03.

Released with Ops Manager 6.0.19 on 2023-10-05

Released with Ops Manager 6.0.18 on 2023-09-07

Released with Ops Manager 6.0.17 on 2023-08-03

Released with Ops Manager 6.0.16 on 2023-07-06

Released with Ops Manager 6.0.15 on 2023-06-15

Released with Ops Manager 6.0.14 on 2023-06-01

Released with Ops Manager 6.0.13 on 2023-05-04

Released with Ops Manager 6.0.12 on 2023-04-07

Release with Ops Manager 6.0.11 on 2023-03-15

Released with Ops Manager 6.0.10 on 2023-03-02

  • The agent now compresses its own rotated logs.

Released with Ops Manager 6.0.9 on 2023-02-02

Released with Ops Manager 6.0.8 on 2023-01-12

Released with Ops Manager 6.0.7 on 2022-12-01

Released with Ops Manager 6.0.6 on 2022-11-08

Released with Ops Manager 6.0.5 on 2022-10-20

  • Removes support for unsetting the global default write concern on MongoDB 5.0 and later. The MongoDB Agent now treats DefaultRWConcern with null or empty values as unmanaged and no longer attempts to unset the value.

Released with Ops Manager 6.0.4 on 2022-10-13

Released with Ops Manager 6.0.3 on 2022-09-01

Released with Ops Manager 6.0.2 on 2022-08-04

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade the MongoDB Agent to 12.0.11.7606 or later or upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 6.0.1 on 2022-07-20

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade the MongoDB Agent to 12.0.11.7606 or later or upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 6.0.0 on 2022-07-19

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade the MongoDB Agent to 12.0.11.7606 or later or upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.22 on 2023-07-31

Released with Ops Manager 5.0.21 on 2023-06-01

Released with Ops Manager 5.0.20 on 2023-03-15

Released with Ops Manager 5.0.19 on 2023-02-09

Released with Ops Manager 5.0.18 on 2023-02-02

Released with Ops Manager 5.0.17 on 2022-11-17

Released with Ops Manager 5.0.16 on 2022-10-20

  • Removes support for unsetting the global default write concern on MongoDB 5.0 and later. The MongoDB Agent now treats DefaultRWConcern with null or empty values as unmanaged and no longer attempts to unset the value.

Released with Ops Manager 5.0.15 on 2022-09-19

  • Prevents unnecessary audit log rotations when using with MongoDB 5.0 releases.

Released with Ops Manager 5.0.14 on 2022-08-04

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.13 on 2022-07-21

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.12 on 2022-06-30

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.11 on 2022-06-02

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.10 on 2022-05-05

Warning

Due to critical issue SERVER-68925, Ops Manager deployments using this version of the MongoDB Agent should not perform automated rolling index builds on clusters running the following MongoDB versions:

  • MongoDB 4.2.19-4.2.22

  • MongoDB 4.4.13-4.4.16

  • MongoDB 5.0.6-5.0.11

  • MongoDB 6.0.0-6.0.1

You can continue to perform manual rolling index builds safely on your clusters. To perform automated rolling index builds safely, upgrade your clusters to:

  • MongoDB 4.2.23 or later

  • MongoDB 4.4.17 or later

  • MongoDB 5.0.12 or later

  • MongoDB 6.0.2 or later

Released with Ops Manager 5.0.9 on 2022-04-07

Released with Ops Manager 5.0.8 on 2022-03-03

Supports MongoDB log rotate configuration and commands for independent log rotation configuration for MongoDB Log and MongoDB Audit Log Files.

Released with Ops Manager 5.0.7 on 2022-02-17

Rejects legacy monitoring and backup agent settings that don't match MongoDB Agent settings when configOverrides field should be used.

Released with Ops Manager 5.0.6 on 2022-01-13

Released with Ops Manager 5.0.5 on 2021-12-02

Released with Ops Manager 5.0.4 on 2021-11-04

Released with Ops Manager 5.0.3 on 2021-10-06

  • Removes support for RHEL/CentOS 6 for the MongoDB Agent.

Released with Ops Manager 5.0.2 on 2021-09-03

Released with Ops Manager 5.0.1 on 2021-08-05

Released with Ops Manager 5.0.0 on 2021-07-13

  • Stops adding MongoDB binaries (such as mongod, mongos, etc.) to the Linux path when installing from RPM and DEB packages.

Released with Ops Manager 4.4.24 on 2022-07-29

Released with Ops Manager 4.4.23 on 2022-07-07

Released with Ops Manager 4.4.22 on 2022-05-05

Released with Ops Manager 4.4.21 on 2022-02-17

Released with Ops Manager 4.4.20 on 2022-01-13

Released with Ops Manager 4.4.19 on 2021-11-16

Released with Ops Manager 4.4.18 on 2021-11-04

  • Removes support for RHEL/CentOS 6 for the MongoDB Agent.

Released with Ops Manager 4.4.17 on 2021-09-03

Released with Ops Manager 4.4.16 on 2021-08-05

Released with Ops Manager 4.4.13 on 2021-06-03

Released with Ops Manager 4.4.12 on 2020-05-06

  • Uses Go 1.15 to build the MongoDB Agent. Before upgrading to this version, ensure that all TLS certificates used in your MongoDB deployment contain a Subject Alternative Name. For more information, see Troubleshooting Automation.

Released with Ops Manager 4.4.11 on 2020-04-01

Released with Ops Manager 4.4.10 on 2020-03-04

Released with Ops Manager 4.4.9 on 2021-02-17

  • Fixes a bug that ensures fixed ordering of index options for all nodes in a rolling index build.

Released with Ops Manager 4.4.7 on 2021-01-11

  • Fixes a bug that can crash the agent after upgrading to Ops Manager 4.4.6 on deployments that use the MongoDB Enterprise Kubernetes Operator.

Released with Ops Manager 4.4.6 on 2020-12-03

Released with Ops Manager 4.4.5 on 2020-11-05

Released with Ops Manager 4.4.4 on 2020-10-07

Released with Ops Manager 4.4.3 on 2020-09-23

Released with Ops Manager 4.4.2 on 2020-09-03

Released with Ops Manager 4.4.1 on 2020-08-05

Released with Ops Manager 4.2.25 on 2021-06-03.

Released with Ops Manager 4.2.24 on 2020-05-05.

  • Uses Go 1.15 to build the MongoDB Agent. Before upgrading to this version, ensure that all TLS certificates used in your MongoDB deployment contain a Subject Alternative Name. For more information, see Troubleshooting Automation.

Released with Ops Manager 4.2.22 on 2020-12-03.

Released with Ops Manager 4.2.21 on 2020-11-05.

Released with Ops Manager 4.2.17 on 2020-09-13

  • Fixes a bug where the MongoDB Agent ignored other agent authentication mechanisms if clusterAuth``was set to ``x509.

Released with Ops Manager 4.2.16 on 2020-08-06

Released with Ops Manager 4.2.15 on 2020-07-02

  • Reduces number of connections per second.

  • Improves the Backup Module oplog tail performance.

Released with Ops Manager 4.2.14 on 2020-06-04

  • Allows Automation for managed deployments to start mongos processes if only the CSRS primary is available, instead of requiring all CSRS members to be available.

  • Fixes a rare issue with managed deployments where the MongoDB Agent is unable to start MongoDB processes.

  • Fixes an issue where the MongoDB Agent ignores other agent authentication mechanisms if clusterAuth is set to x509.

Released with Ops Manager 4.2.13 on 2020-05-14

  • Fixes an issue with managed deployments that can occur when a sharded cluster has a shard added and an index built at the same time.

  • Supports SUSE 15.

Released with Ops Manager 4.2.12 on 2020-04-09

  • Fixes an issue that resulted in failures creating snapshots when handling sessions between the MongoDB Agent and MongoDB 4.2 clusters.

Released with Ops Manager 4.2.11 on 2020-04-06

  • Ensures that the MongoDB Agent never interprets network errors as authentication configuration errors, leading to illegitimate attempts to rotate the keyfile.

Released with Ops Manager 4.2.10 on 2020-03-16

  • Ensures that an error when rotating one type of log file does not interfere with log rotation of other log files.

  • Ensures that the MongoDB Agent always respects the optionality of keyfiles for MongoDB deployments using X-509 cluster authentication.

  • Ensures that a majority of healthy nodes remains up at all times if a cluster has unhealthy nodes prior to the initiation of a storage-affecting rolling change.

  • Ensures that when importing a new sharded cluster for monitoring, the algorithm for auto-discovering all processes in the sharded cluster will also consider the fully qualified domain names.

  • Upgrades the backup module of the MongoDB Agent to use the MongoDB Go Driver version 1.1.4.

Released with Ops Manager 4.2.9 on 2020-03-05

  • Ensures that an error when rotating one type of log file does not interfere with log rotation of other log files.

  • Ensures that the MongoDB Agent always respects the optionality of keyfiles for MongoDB deployments using X-509 cluster authentication.

  • Ensures that a majority of healthy nodes remains up at all times if a cluster has unhealthy nodes prior to the initiation of a storage-affecting rolling change.

  • Upgrades the backup module of the MongoDB Agent to use the MongoDB Go Driver version 1.1.4.

Released with Ops Manager 4.2.8 on 2020-02-06

  • Adds support for management of MongoDB deployments on Debian 10.

  • Fixes the following issues:

    • During a rolling index build for an unsharded collection on a sharded collection, only index the collection on the shard on which it already exists.

    • When the MongoDB Agent authenticates to MongoDB clusters using GSSAPI authentication, ensure that Ops Manager falls back to other authentication methods if the kinit call fails.

  • Can perform a restore to a cluster that is unhealthy before the restore is requested.

  • Redacts sensitive configuration data in MongoDB Agent log files to improve security.

Released with Ops Manager 4.2.7 on 2020-01-09

  • Improves the behavior when a rollback occurs on a source cluster using replication protocol v0 when backing up clusters running MongoDB 4.0 and earlier.

Released with Ops Manager 4.2.6 on 2019-12-19

  • Resolves memory leak in MongoDB Agent when performing snapshots for MongoDB 4.2 clusters.

Released with Ops Manager 4.2.5 on 2019-12-12

  • MongoDB Agent is now built using Go 1.13.

Released with Ops Manager 4.2.4 on 2019-11-07

  • MongoDB Agent is now built using Go 1.13.

  • Fixes an issue where the MongoDB Agent fails to complete some requested actions on a sharded cluster if a config server is down.

  • When creating an index using Data Explorer, the optional name property of an index is no longer ignored.

Released with Ops Manager 4.2.3 on 2019-10-10

Released with Ops Manager 4.2.2 on 2019-10-03

  • Adds support for the businessCategory field in extended validation TLS certificates.

  • MongoDB Agent is now built using Go 1.12.

  • Adds support for the partialFilterExpression index option when creating an index using Data Explorer.

  • Backup: Adds support for the businessCategory field in extended validation TLS certificates.

  • Monitoring: Adds support for the businessCategory field in extended validation TLS certificates.

Released with Ops Manager 4.2.1 on 2019-09-05

  • Fixes a bug where the MongoDB Agent could panic and delete files from its current working directory.

  • Improves logging in the MongoDB Agent such that when a connection to a MongoDB process is deliberately canceled, it does not appear as an error.

←  Ops Manager Server ChangelogAutomation Agent Changelog →

On this page