With Diagnostics 3.1, we introduce a release focused on simplifying deployment, modernizing the platform, and improving overall stability. The most significant change is the introduction of a Docker-based deployment option for the Collector, making installation and updates easier than ever.

Docker image for the Collector

Diagnostics 3.1 adds an official Docker image (including a compose.yaml) for running the Collector on Linux.
This new option removes the dependency on JSVC and provides a cleaner, more reliable way to install, configure, and maintain the Diagnostics Collector.
The traditional .rpm installer remains part of the package for customers who need it, but we recommend Linux users transition to the Docker deployment going forward.

Java 11 requirement

To stay aligned with updated external libraries, Diagnostics now requires Java 11. This applies to both the Archiver ACP and the Collector. They can each be configured to use a specific Java runtime.

 

Enhancements and fixes

Diagnostics 3.1 includes a number of improvements across the platform:

  • Improved feedback when permissions are insufficient in the Environments and Users dashboards.
  • Prevented power users from modifying out‑of‑the‑box dashboards.
  • The action_timestamp field has been replaced with _time, which automatically uses the user’s local timezone.
  • Updated all external libraries to current compatible versions.
  • Fixed negative values that could appear in the Dataset usage dashboard when using short transactions.
  • Removed outdated references to “index” where “environment” is now the correct term.
  • Added documentation for rwx_ds_latency.

For a detailed overview of all the changes, please check our Release Notes.

If you’d like help switching your Collectors to Docker or upgrading from an older release, our team is ready to support you.

Diagnostics 3: Bringing insight out