« Changelog History


Sensu v1.3.0 Release Notes

Release Date: 2018-03-09 // about 6 years ago

  • 🛠 Fixed

    • Sensu TCP event handlers will no longer connect to a socket if the provided event data is nil or empty. (#1734)
    • 🛠 The RabbitMQ transport will now reconnect after failing to resolve DNS, instead of independently retrying broker hostname resolution. This fixes retry timer backoff and allows the transport to connect to another eligible broker after failing to resolve a hostname.

    ➕ Added

    • Redis TLS connection support. Sensu Redis connections can now be configured to use TLS, this includes the Sensu server and Redis transport connections! The Sensu Redis configuration definition now includes the optional "tls" (or "ssl") attribute, a hash containing TLS options ("private_key_file", "cert_chain_file", and "verify_peer").
    • 🔧 The Sensu client TCP/UDP socket can now be disabled via configuration.
    • 🔧 The Sensu client configuration definition now includes the socket "enabled" attribute, which defaults to true, and it can be set to false in order to disable the socket. (#1799)
    • 🔒 The Sensu Ruby gems are now cryptographically signed. To learn more about Ruby gem signing, please refer to the RubyGems security guide. (#1819)
    • The Sensu API POST /clients endpoint no longer requires client subscriptions to be specified. (#1795)
    • 🌲 All Sensu event handler types now include event ID in log events.