This release brings together a number of bug fixes and improvements:

Metrics - the metric charts were not always displaying
Schema filtering - some elements in the schema would cause the application to crash
Postgres can now listen to non-default schemas

Metrics

Metrics allow real-time measurement of activity in graphs and are shown within a journey map attached to journey steps. These metric values can be viewed in the journey map by pinning the metrics to journey steps or on the metric tab in the project home page. Unfortunately depending on how busy the metric subsystem was it was not always possible to display the metric charts.

The dataflow for the metric calculations has been reworked to make access to metric values immediate without being affected by the volume of metrics being processed.

Schema Filtering

A bug was introduced which was sensitive to arrays in the schema. Typing the name of an array entity in the search filter would cause the application to crash and a browser reload was required. This has now been fixed and filtering should work as normal.

Postgres Schema

Previously it was not possible to listen to a non-default schema in a Postgres database. The listen query would not allow fully qualified table names of the form schema.table. This change allows these table names to be used in listen queries. This format was already supported in the other database adaptor methods for Postgres.

Bug Fixes

[KIT-2123] - Fixed issue that was causing visual testing to fail without feedback to the user
[KIT-2058] - Postgres Can Not Listen to a table that is not in the user's default schema
[KIT-2097] - Schema filtering throws error if schema contains an array
[KIT-1991] - Rework data storage and query pattern for time based metrics to make it more efficient and consistent

Browser not supported