« Changelog History


Sensu v0.27.0 Release Notes

Release Date: 2017-01-26 // about 7 years ago

  • 💥 Breaking Changes

    • The CONFIG_DIR environment variable has been renamed to CONFD_DIR. This environment varible is used to specify the directory path where Sensu processes will load any JSON config files for deep merging. If you are using /etc/default/sensu to specify a custom value for CONFIG_DIR, please update it to the new CONFD_DIR variable name.

    🛠 Fixed

    • Silenced resolution events with silencing "expire_on_resolve": true are now handled.

    ➕ Added

    • 🔧 Sensu client HTTP socket for check result input and informational queries. The client HTTP socket provides several endpoints, /info, /results, and /settings. Basic authentication is supported, which is required for certain endpoints, i.e. /settings. The client HTTP socket is configurable via the Sensu client definition, "http_socket": {}.
    • Hostnames are now resolved prior to making connection attempts, this applies to the Sensu Transport (i.e. RabbitMQ) and Redis connections. This allows Sensu to handle resolution failures and enables failover via DNS and services like Amazon AWS ElastiCache.
    • ➕ Added API endpoint /silenced/ids/:id for fetching a silence entry by id.
    • ➕ Added check attribute ttl_status, allowing checks to set a different TTL event check status (default is 1 warning).
    • ➕ Added client deregistration attribute status, allowing clients to set a different event check status for their deregistration events (default is 1 warning).
    • ➕ Added Rubygems cleanup support to sensu-install, via the command line argument -c/--clean when installing one or more plugins and/or extensions. If a version is provided for the plugin(s) or extension(s), all other installed versions of them will be removed, e.g. sensu-install -e snmp-trap:0.0.19 -c. If a version is not provided, all installed versions except the latest will be removed.

    🔄 Changes

    • ➕ Added the filter name to event filtered log events.
    • Check TTL events now have the check interval overridden to the TTL monitoring interval, this change allows event occurrence filtering to work as expected.