Sensu v0.11.0 Release Notes
Release Date: 2013-10-02 // over 10 years ago-
💥 Breaking Changes
- ⚡️ Extensions compatible with previous versions of Sensu will NO LONGER FUNCTION until they are updated for Sensu 0.11.x! Extensions are an experimental feature and not widely used.
Sensu settings are now part of the extension API & are no longer passed as an argument to run.
⏱ TCP handlers no longer have a socket timeout, instead they have a ⏱ handler timeout for consistency.
🛠 Fixed
- Sensu passes a dup of event data to mutator & handler extensions to prevent mutation.
- Extension runs are wrapped in a begin/rescue block, a safety net.
- UDP handler now binds to "0.0.0.0".
- 📜 Faster JSON parser.
- AMQP connection heartbeats will no longer attempt to use a closed channel.
- Missing AMQP connection heartbeats will result in a reconnect.
- The keepalive & result queues will now auto-delete when there are no active consumers. This change stops the creation of a keepalive/result backlog, stale data that may overwhelm the recovering consumers.
- 👌 Improved Sensu client socket check validation.
- AMQP connection will time out if the vhost is missing, there is a lack of permissions, or authentication fails.
➕ Added
- 🌲 You can specify the Sensu log severity level using the -L (--log_level) CLI argument, providing a valid level (eg. warn).
- You can specify custom sensitive Sensu client key/values to be redacted from log events and keepalives, eg.
"client": { "redact": [ "secret_access_key" ] }. - 🔧 You can configure the Sensu client socket (UDP & TCP), bind & port, eg.
"client": { "socket": { "bind": "0.0.0.0", "port": 4040 } }. - ⏱ Handlers & mutators can now have a timeout, in seconds.
- 🔧 You can configure the RabbitMQ channel prefetch value (advanced), eg. "rabbitmq": { "prefetch": 100 }.