and in case you missed 4.0 release, here’s what has changed:
This release brings several bug fixes, improvements, and new features. Following our naming convention, some of those improvements and fixes introduced breaking changes which means we must bump the version to 4.x as it impossible to upgrade from 3.x without migration scripts. If you are on 3.x or earlier version, you must deploy this release as a new database.
This release also brings several improvements to the way release notes are published and to the internal testing process. Hopefully from now on we should be able to release more often and with better release notes.
Added ability to collect performance counters via CLR. This is experimental for now and not enabled and does not require CLR to be enabled unless you want to use this functionality. More details in #256 (1870cad, 58bd284, 98a2c9d, 2c1849e, 758c1c2 by @marcingminski)
Customisable baselines allowing to “freeze” data and prevent it from being deleted by the retention. Baselines can now be used in Checks as they can check for deviation from the baseline as well as deviation from the set value. Future releases will introduce changes to the Dashboards to be able to show them (7abde20, 03a9ebb, d6ef25e, 9e61e28, 942dd26, 72faa1a by @marcingminski)
Change dispatch of SQLWATCH_blockers XES to 1 second to be able to capture chains as soon as they appear to show on Dashboard (35553e1 by @marcingminski)
Added condition to check for SQL Agent when deploying SQLWATCH so if the agent is stopped, we will not attempt to deploy agent jobs as it would fail. They can be deployed later via stored procedure (cf87787 by @marcingminski)