...

Here is what is included in the release.

...

Product Release

Added

Tomcat logs can now be set up to automatically be removed after a certain number of days. This behaviour is governed by a new setting available:

...

This new setting also dictates the turnover of a new, daily rotating log file name out.{date}.log.

This new file is where log messages from the Dashboard are written. The default value for this setting is 0 which means that no logs will be removed.

It is now possible to set a start and end drill level that a user can see when looking at a chart when it is embedded. For instance in a chart with 5 drill levels, it would be possible to have some users that can see levels 2-4. When skipping the top levels, no filter will be applied to the chart that is seen by the user.

...

Further documentation on restricting drill levels when embedding charts can be found here.← THIS LINK CURRENTLY LINKS TO A DRAFT. THE DRAFT WILL NEED TO GO LIVE BEFORE THE RELEASE NOTES GO OUT.on our Embedding pages.

To enhance our scaling capabilities we now have support for using Redis to store session data. This allows you to run multiple Dashboard instances in a load balanced environment with a single, fast store of session data.

To see how to use this have a look at our documentation and docker-compose example -

NEIL TO ADD EXAMPLE DOCKER COMPOSE AND DOCS

The ‘Drill to top on full screen close’ option added last month didn’t support ‘Drill to Chart’. Now, once this option or the related ‘Full screen to display this level’ are set to True that drill level and any below it will reflect that behaviour - even if you have drilled to another chart.

The two fields are now independent of one another. When editing a chart, you will be able to tell when a drill level has one/both of these settings overridden by a higher drill level as they will be disabled, appear as checked, and a warning icon with a helpful, on-hover tooltip will be displayed next to them. Please note, the field appearing as checked when disabled does not relate to its value in the database it is a visualisation of the expected behaviour.

...

...

Changed

To resolve reported vulnerabilities in the base used for our container images all supported images have been either updated or rebased and updated to resolve these issues. As a result of using more lightweight base images over 150 MiB has been saved from the images.

The Athena JDBC driver provided by Amazon has been upgrade to remove some reported vulnerabilities.

JDom, AWS Marketplace and Java SAML libraries have been upgraded to resolve reported vulnerabilties

...

Fixed

The category panel unpin label had an incorrect label, this has been resolved, the wording has also been improved.

...

Previously, when embedding 2 categories in 1 html page with 2 different category modes, the category modes would conflict and you would get inconsistent behaviour where sometimes it would wrongly use the same category mode for both embedded categories. Now, each embedded category uses its defined mode correctly.

Previously when running the dashboard on Windows, the Scheduler was unable to pick up and use the correct time zone. This meant that the times in the monitoring screen were incorrect, and the scheduler logs would fill up with errors. This has now been fixed.

The wrong encoding format was being used on the url feedback snack bar when using single-chart mode. This has now been resolved improving both the security and display user experience.

...