With version 6.0.0, Java 17 is required as Java for the CHRONOS Server, AdminSuite FX and Archive Explorer. However, the CHRONOS JDBC driver can still be accessed with Java 8.
It is now possible to check the CHRONOS processes via external dashboards.
Server & job status (running, successful, faulty jobs) and system load can be viewed.
Azure Monitor, Elastic, Prometheus and others are supported.
A possible display with Grafana could look like this:
Mark/delete job flags can now be set per M/L configuration, whether the flag should be set or left blank in the event of a database error.
If the flags are left blank, the tag can be checked again the next time an M/L job is started.
In addition, the detailed tagging & deletion job logs have been extended for even better error analysis.
The Search Performance Tester offers the option of executing self-configured search queries at specific times in order to automatically check whether there is a decrease or increase in performance.
If there is a decrease in performance, an e-mail is sent to the user.
The executed searches, job ID 318704 is above the tolerance limit and therefore not OK.
The Index Checker job automatically retrieves missing binary search indexes. The job has been designed to use CPU resources sparingly. The Index Checker job must be activated explicitly for each archive configuration.
CHRONOS now supports the CyberArk interface "Central Credential Provider Web Service", which - if authorized - transmits the current passwords to CHRONOS. This means that it is no longer necessary to manually save or change database passwords in CHRONOS.
CHRONOS now updates its repository database automatically from version 6.0.0.
It is no longer necessary to import manual update scripts when updating a version.
The logic for loading the metadata of the archiving databases has been revised, which has increased the loading speed.
Of course, the "classic" CHRONOS will continue to be equipped with features and bug fixes.