Changelog

NOTE: Although we endeavor to keep this combined changelog up-to-date, the official Sensu Core changelog may describe changes not yet documented here.

Releases

Enterprise 1.13.0 Release Notes

June 9, 2016 — Sensu Enterprise version 1.13.0 has been released and is available for immediate download. Please note the following improvements:

IMPORTANT

This release includes potentially breaking, backwards-incompatible changes:

  • This is the first Sensu Enterprise release based on Sensu Core version 0.24.x. Please refer to the Sensu Core version 0.24.0 release notes for additional information on potentially breaking changes. This release requires Sensu Enterprise Dashboard 1.9.8 or higher.

CHANGES

Core 0.24.1 Release Notes

Source: GitHub.com

June 7, 2016 — Sensu Core version 0.24.1 has been released and is available for immediate download. Please note the following improvements:

  • BUGFIX: Fixed a critical bug in Sensu server resume() which caused the server to crash when querying the state of the Sensu Transport connection before it had been initialized. Resolves #1321.

  • IMPROVEMENT: Updated references to unmatched tokens, i.e. check result output message, to better represent the new scope of token substitution. Resolves #1322.

Core 0.24.0 Release Notes

Source: GitHub.com

June 6, 2016 — Sensu Core version 0.24.0 has been released and is available for immediate download. Please note the following improvements:

IMPORTANT

This release includes potentially breaking, backwards-incompatible changes:

  • Sensu check aggregates have been completely redesigned. Users who are using check aggregates may need to review these changes before upgrading. Uchiwa users should install version 0.15 or higher before upgrading to Sensu Core version 0.24.0. See below for additional information.

  • Sensu event ids are no longer unique to each occurrence of an event. Event ids are now persistent for the duration of an event (per client/check pair), until the event is resolved. See below for additional information.

  • The Sensu /health (GET) API endpoint has been updated such that failed health checks now respond with an 412 (Precondition Failed) HTTP response code instead of a 503 (Service Unavailable) response code. Third-party services and/or custom scripts may need to be updated accordingly.

  • The Sensu services and corresponding service management scripts have been updated to use the new --validate_config command line option which uses strong configuration validation (i.e. do not start if configuration is in an invalid state). See below for additional information.

CHANGES

  • NEW: Named aggregates. Check aggregates 2.0 are here! At long last, Sensu check aggregates have been updated to support standalone checks, as well as a number of new use cases. Please refer to the check aggregates reference documentation for additional information. Resolves #803, #915, #1041, #1070, #1187, and #1218.

  • NEW: Persistent event IDs. Event occurrences for a client/check pair will now have the same event ID until the event is resolved (instead of a unique event ID for each occurrence of an event). Please refer to the Event specification reference documentation for additional information. Resolves #1196.

  • NEW: Strong configuration validation. Added a new --validate_config CLI option/argument to cause Sensu to validate configuration settings and exit with the appropriate exit code (e.g. 2 for invalid). This feature is now used when restarting a Sensu service to first validate the new configuration before stopping the running service (i.e. to prevent restarts if the configuration is invalid). Please refer to the Sensu service command line interface reference documentation for additional information. Resolves #1244, #1254.

  • NEW: Proxy check origins. Events for proxy clients will now have a check origin attribute, set to the client name of the result producer. Please refer to the Event data specification reference documentation for additional information. Resolves #1075.

  • NEW: Improved Sensu check token substitution. Sensu check token substitution is now supported in every check definition attribute value (no longer just the check command attribute). Please refer to the check token substitution reference documentation for additional information. Resolves #1281.

  • NEW: Sensu /clients (POST) API endpoint can now create clients in the client registry that are expected to produce keepalives, and validates clients with the Sensu Settings client definition validator. A new check keepalives attribute called has also been added, which allows client keepalives to be disabled on a per-client basis. Resolves #1203.

  • IMPROVEMENT: Configurable Sensu Spawn concurrent child process limit (checks, mutators, & pipe handlers). The default limit is still 12 and the EventMachine threadpool size is automatically adjusted to accommodate a larger limit. Resolves #1002.

  • IMPROVEMENT: Event data check type now explicitly defaults to standard. Resolves #1025.

  • IMPROVEMENT: Improved tracking of in progress check result processing, eliminates the potential for losing check results when restarting the Sensu server service. Resolves #1165.

  • IMPROVEMENT: Updated Thin (used by Sensu API) to the latest release, version 1.6.4. Resolves #1122.

  • IMPROVEMENT: JrJackson is now used to parse JSON when Sensu is running on JRuby.

  • IMPROVEMENT: The Sensu API now listens immediately on service start, even before it has successfully connected to Redis and the Sensu Transport. It will now respond with a 500 (Internal Server Error) HTTP response code and a descriptive error message when it has not yet initialized its connections or it is reconnecting to either Redis or the Sensu Transport. The Health and Info API endpoints will still respond normally while reconnecting. Resolves #1215.

Start your FREE trial today.

Already using Sensu Core? Upgrade to Sensu Enterprise today to take advantage of its enterprise console, added-value features, built-in integrations, FREE annual training, and enterprise-class support.