UnboundID Metrics Engine Release Notes

UnboundID Logo
  Return to Documentation Index

Metrics Engine 3.5.1.9

Following are notes for version 3.5.1.9 of the UnboundID Metrics Engine. Notes for the following versions of the Metrics Engine are also available in this document:

Resolved Issues

The following issues have been resolved with this release of the Metrics Engine:

No information is available

Metrics Engine 3.5.1.3

Resolved Issues

These issues were resolved with version 3.5.1.3 of the Metrics Engine:

No information is available

Metrics Engine 3.5.1.2

Resolved Issues

These issues were resolved with version 3.5.1.2 of the Metrics Engine:

  • Fix an issue where dsconfig could apply changes to multiple servers in a failure situation even though it claimed that no changes were applied. Issue:DS-8677

Metrics Engine 3.5.1.1

Resolved Issues

These issues were resolved with version 3.5.1.1 of the Metrics Engine:

  • Fix a bug in dsconfig that prevented going back when adding a new configuration object inside of an existing one. Issue:DS-7263 SF#:1793

  • Prevent disk space monitoring for metrics db for environments where file permissions disallow reading. Issue:DS-7266 SF#:1794

Metrics Engine 3.5.1.0

New Features

These features were added for version 3.5.1.0 of the Metrics Engine:

  • The Metrics Engine is a core server product that collects and aggregates key diagnostic, capacity, and usage information from an UnboundID server topology consisting of instrumented Directory Server, Directory Proxy Server, and Synchronization Servers running release 3.5.0.0 and above. Metrics data can be explored and graphed using the included query-metric tool, and the Metrics Engine REST API makes this information available to custom applications and third-party systems. To learn more about the Metrics Engine, please refer to the UnboundID Metrics Engine Administration Guide.

Known Issues and Workarounds

These were known issues at the time of the release of version 3.5.1.0 of the Metrics Engine:

Resolved Issues

These issues were resolved with version 3.5.1.0 of the Metrics Engine:

No information is available