1. VSD 5.6.3 Release Notes

Overview

Visual Statistics Display (VSD) version 5.6.3 is a new release of the VSD product, fixing several significant bugs.

These release notes describe changes between the previous version of VSD, version 5.6.1, and version 5.6.3.

This version of VSD supports statmonitor files generated from:

Supported Platforms

VSD version 5.6.3 is verified and supported on the following platforms:

VSD is expected to work on older versions of these platforms, but end-of-life platform versions are not officially supported.

Changes in this Release

New display control No All Zeros

VSD has an existing display control, No Flatlines, which is designed to hide uninteresting zero statistics. This both limits the specific list of statistics that is displayed on the main page, and also prevents including lines for these statistics if the line would be flat (that is, the value does not change in the life of the statmonitor data).

This can hide information for counter type stats, in the case that the underlying data is not zero but does not change. These statistics are included in the display list of statistics, since they are not zero. Since counter type stats display as changes per second, a constant data value results in a flat line of zero.

The new display control, No All Zeros, has the same effect on the list of displayed statistic names as No Flatlines. When No All Zeros is used rather than No Flatlines, counter stats with nonzero values are included in the chart, with flat lines at 0. To see the actual value, you must change the filter from Per Second to No Filter.

No Flatlines and No All Zeros are mutually exclusive; selecting one deselects the other.

ReclaimGem session stats not applied in v3.7.1.x and later

VSD automatically applies aliases to session stats according to the server-version specific definitions. These were not recognizing some version numbers. (#51493)

When monitoring GS64 v3.7.2 and later, stop monitoring does not work

VSD allows you to start and stop collecting statistics on a running Stone. Due to changes in signal handling, with v3.7.2 and later stones, VSD stop monitoring was ignored. (#51447)

Line trim may crash VSD

If trimming a line to the right, VSD code may SEGV, due to issues handling timestamps for multiple lines. (#51318)