...

Here is what is included in the release.

...

Product Release

Added

The ‘Drill to top on full screen close’ option added last month didn’t support (introduced in our September 23 release) now supports the ‘Drill to Chart’ option.

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 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.

...

It is now possible to set a start Start and end End drill level that a user can see when looking at viewing a chart - when it is embedded. For example in

As an example, where a chart with has 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.

You can set the values for drillStart and drill End drillEnd as query parameters on the URL that you are using to embed.

When setting a drillStart you will also need to supply the identifiers for the chart and hierarchy levels of the drill levels above the start, and the drill level you wish the user to see by manipulating the URL directly.

These must be separated by the !$! delimiter when adding multiple levels. When drilling to the top, the user will return the level defined as the drillStart parameter. It is possible to use the parameters individually or together.

...

Further documentation on restricting drill levels when embedding charts can be foundon our Embedding pages.

...

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

• Under the Tomcat tab of the Configuration-Tool GUI under a new ‘Logging’ section (see picture below)

• Under the Tomcat > Logging section of the dashboard.json file

• Set via the PI_TOMCAT_LOGGING_MAX_AGE environment variable

...

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.

...

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.

...

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 upgraded updated to remove some address reported vulnerabilities.

JDom, AWS Marketplace and Java SAML libraries have been upgraded to resolve remain updated with the latest features, and to address reported vulnerabilities.

...

Fixed

The category Category panel unpin label had an incorrect label, this has been resolved, the wording has also been improved/description was incorrectly worded, which has been rectified as per the image below.

...

...

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

Previously when 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 An incorrect encoding format was being used on applied to the URL feedback snack bar, when using single-chart mode. This has now been resolved The resolution helps improving both the security and user display user experienceexperiences.

...