All Versions
100
Latest Version
Avg Release Cycle
38 days
Latest Release
1925 days ago

Changelog History
Page 3

  • v1.1.1 Changes

    October 10, 2017

    🛠 Fixed

    • 🛠 Fixed a bug in check TTL monitoring that caused the Sensu server to crash. Check TTL member deletion, following the deletion of the associated check result, would produce an uncaught error.

  • v1.1.0 Changes

    September 27, 2017

    🛠 Fixed

    • ➕ Added initial timestamp to proxy client definitions. The Uchiwa and Sensu dashboards will no longer display "Invalid Date".
    • Deleting check history when deleting an associated check result.

    ➕ Added

    • 🚑 Check hooks, commands run by the Sensu client in response to the result of the check command execution. The Sensu client will execute the appropriate configured hook command, depending on the check execution status (e.g. 1). Valid hook names include (in order of precedence): "1"-"255", "ok", "warning", "critical", "unknown", and "non-zero". The check hook command output, status, executed timestamp, and duration are captured and published in the check result. Check hook commands can optionally receive JSON serialized Sensu client and check definition data via STDIN.
    • 🔌 Check STDIN. A boolean check definition attribute, "stdin", when set to true instructs the Sensu client to write JSON serialized Sensu client and check definition data to the check command process STDIN. This attribute cannot be used with existing Sensu check plugins, nor Nagios plugins etc, as the Sensu client will wait indefinitely for the check process to read and close STDIN.
    • 🔧 Splayed proxy check request publishing. Users can now splay proxy check requests (optional), evenly, over a window of time, determined by the check interval and a configurable splay coverage percentage. For example, if a check has an interval of 60s and a configured splay coverage of 90%, its proxy check requests would be splayed evenly over a time window of 60s * 90%, 54s, leaving 6s for the last proxy check execution before the the next round of proxy check requests for the same check. Proxy check request splayed publishing can be configured with two new check definition attributes, within the proxy_requests scope, splay (boolean) to enable it and splay_coverage (integer percentage, defaults to 90).
    • Configurable check output truncation (for storage in Redis). Check output truncation can be manually enabled/disabled with the check definition attribute "truncate_output", e.g."truncate_output": false. The output truncation length can be configured with the check definition attribute "truncate_output_length", e.g. "truncate_output_length": 1024. Check output truncation is still enabled by default for metric checks, with "type": "metric".
    • Sensu client HTTP socket basic authentication can how be applied to all endpoints (not just /settings), via the client definition http_socket attribute "protect_all_endpoints", e.g. "protect_all_endpoints": true.

    Other

    👌 Improved check TTL monitoring performance.

    🌲 The Sensu extension run log event log level is now set to debug (instead of info) when the run output is empty and the status is 0.

  • v1.0.3 Changes

    August 25, 2017

    🛠 Fixed

    • ⏱ Now using EventMachine version 1.2.5 in order to support larger EM timer intervals. EM timers are used by the Sensu check scheduler and many other Sensu components.

  • v1.0.2 Changes

    July 27, 2017

    🛠 Fixed

    • ➕ Addressed an issue with client keepalive transport acknowledgments. We discovered a situation where poor Redis performance could negatively impact client keepalive processing, potentially triggering a compounding failure that the Sensu server is unable to recover from. Moving acknowledgments to the next tick of the EventMachine reactor avoids the situation entirely.

  • v1.0.1 Changes

    July 24, 2017

    🛠 Fixed

    • 🛠 Fixed Sensu configuration validation, it was not being applied.

  • v1.0.0 Changes

    July 11, 2017

    🛠 Fixed

    • Sensu handler severities filtering now accounts for flapping events.
    • 🛠 Fixed Sensu Redis connection on error reconnect, no longer reusing the existing EventMachine connection handler.

    ➕ Added

    • ➕ Added Sensu API event endpoint alias "incidents", e.g. /incidents, /incidents/:client/:check.

    🔄 Changed

    • 👌 Improved Sensu client keepalive configuration validation, now including coverage for check low/high flap thresholds etc.
    • 👌 Improved Sensu client socket check result validation, now including coverage for check low/high flap thresholds etc.

    • 💎 The sensu-install tool now notifies users when it is unable to successfully install an extension, when the environment variable EMBEDDED_RUBY is set to false.

    • ➕ Added the Sensu RELEASE_INFO constant, containing information about the Sensu release, used by the API /info endpoint and Server registration.

  • v0.29.0 Changes

    March 29, 2017

    🛠 Fixed

    • 👍 The built-in filter occurrences now supports refresh for flapping events (action flapping).
    • 🔧 Force the configured Redis port to be an integer, as some users make the mistake of using a string.

    ➕ Added

    • Sensu server tasks, replacing the Sensu server leader functionality, distributing certain server responsibilities amongst the running Sensu servers. A server task can only run on one Sensu server at a time. Sensu servers partake in an election process to become responsible for one or more tasks. A task can failover to another Sensu server.
    • Sensu API response object filtering for any GET request. Filtering is done with one or more dot notation query parameters, beginning with filter., to specify object attributes to filter by, e.g. /events?filter.client.environment=production&filter.check.contact=ops.
    • ➕ Added API endpoint GET /settings to provided the APIs running configuration. Sensitive setting values are redacted by default, unless the query parameter redacted is set to false, e.g. /settings?redacted=false.
    • Added support for invalidating a Sensu client when deleting it via the Sensu API DELETE /clients/:name endpoint, disallowing further client keepalives and check results until the client is either successfully removed from the client registry or for a specified duration of time. To invalidate a Sensu client until it is deleted, the query parameter invalidate must be set to true, e.g. /clients/app01.example.com?invalidate=true. To invalidate the client for a certain amount of time (in seconds), the query parameter invalidate_expire must be set as well, e.g. /clients/app01.example.com?invalidate=true&invalidate_expire=300.
    • ➕ Added a Sensu settings hexdigest, exposed via the Sensu API GET /info endpoint, providing a means to determine if a Sensu server's configuration differs from the rest.
    • ➕ Added a proxy argument to sensu-install. To use a proxy for Sensu plugin and extension installation with sensu-install, use the -x or --proxy argument, e.g. sensu-install -e statsd --proxy http://proxy.example.com:8080.
    • ➕ Added support for issuing proxy check requests via the Sensu API POST /request endpoint.
    • 🔊 The Sensu API now logs response times.
    • 👍 The Sensu API now returns a 405 (Method Not Allowed) when an API endpoint does not support a HTTP request method, e.g. PUT, and sets the HTTP header "Allow" to indicate which HTTP request methods are supported by the requested endpoint.
    • ➕ Added a built-in filter for check dependencies, check_dependencies, which implements the check dependency filtering logic in the Sensu Plugin library.
    • Added default values for Sensu CLI options config_file ("/etc/sensu/config.json") and config_dirs (["/etc/sensu/conf.d"]). These defaults are only applied when the associated file and/or directory exist.

    🔄 Changed

    • ➕ Added a Rubocop configuration file and rake tasks for a slow introduction.

  • v0.28.5 Changes

    March 23, 2017

    🛠 Fixed

    • 🛠 Fixed check subdue and filter when features when a time window spans over 00:00:00, crossing the day boundary.

  • v0.28.4 Changes

    March 10, 2017

    🛠 Fixed

    • ⏱ In the interest of addressing a regression causing duplicate check execution requests, code added in 0.28.0 to account for task scheduling drift has been removed.

  • v0.28.3 Changes

    March 09, 2017

    🛠 Fixed

    • The Sensu client now includes check source when tracking in progress check executions. These changes are necessary to allow the Sensu client to execute on several concurrent proxy check requests.