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

Changelog History
Page 4

  • v0.28.2 Changes

    March 03, 2017

    🛠 Fixed

    • Clients created via /clients API endpoint now have a per-client subscription added automatically, ensuring they can be silenced.

  • v0.28.1 Changes

    March 01, 2017

    🛠 Fixed

    • Check requests with proxy_requests attributes are no longer overridden by local check definitions.
    • 🚀 Updated Oj (used by the sensu-json library) to the latest release (2.18.1) for Ruby 2.4 compatibility.

  • v0.28.0 Changes

    February 23, 2017

    🛠 Fixed

    • ⏱ The Sensu interval timers, used for scheduling tasks, now account for drift. The check request and standalone execution scheduler timers are now more accurate.
    • 🛠 Fixed a bug in the Sensu deep_merge() method that was responsible for mutating arrays of the original provided objects.

    ➕ Added

    • 🔧 Added proxy check requests to improve Sensu's ability to monitor external resources that have an associated Sensu proxy client. Publish a check request to the configured subscribers (e.g. ["round-robin:snmp_pollers"]) for every Sensu client in the registry that matches the configured client attributes in client_attributes on the configured interval (e.g. 60). Client tokens in the check definition (e.g. "check-snmp-if.rb -h :::address::: -i eth0") are substituted prior to publishing the check request. The check request check source is set to the client name.
    • ⏱ Schedule check requests and standalone executions with the Cron syntax.
    • ➕ Added the Sensu server registry, containing information about the running Sensu servers. Information about the Sensu servers is now accessible via the Sensu API /info endpoint.
    • ➕ Added two optional attributes to Sensu API POST /request, "reason" and "creator", for additional context. The check request reason and creator are added to the check request payload under "api_requested" and become part of the check result.
    • ➕ Added event IDs to event handler log events for additional context, making it easier to trace an event through the Sensu pipeline.

  • v0.27.1 Changes

    February 17, 2017

    🛠 Fixed

    • 🏁 Check subdue and filter when time windows now account for GMT offsets.
    • 🚚 Non UTF-8 characters in check tokens are now removed.
    • 🛠 Fixed filter name logging when an event is filtered.

    🔄 Changed

    • 🌲 Failed pipe handler executions are now logged with the error log level.
    • Sensu server now adds a unique per-client subscription to client keepalives when missing. This is to enable built-in event silencing for older Sensu clients (< 0.26).

  • v0.27.0 Changes

    January 26, 2017

    💥 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.

  • v0.26.5 Changes

    October 12, 2016

    🛠 Fixed

    • 🔧 Sensu client no longer fails to validate the client configuration when the automatic per-client subscription is the client's only subscription.

  • v0.26.4 Changes

    October 05, 2016

    🛠 Fixed

    • Sensu check extension executions are now properly tracked and the Sensu client now guards against multiple concurrent executions of the same extension.

  • v0.26.3 Changes

    September 21, 2016

    🛠 Fixed

    • Adjusted regular expression pattern to completely address scenarios where valid subscription names were not allowed via API /silenced/subscriptions/:subscription endpoint, e.g. client:foo-bar-baz.

  • v0.26.2 Changes

    September 20, 2016

    🛠 Fixed

    • ➕ Added logic to ensure proxy clients receive a per-client subscription upon creation so that they can be silenced via /silenced API.
    • Updated API publish_check_result helper to address a condition where events could not be successfully deleted for clients configured with a signature.
    • 🛠 Fixed regexp in API which prevented retrieval of silence entries when requesting subscriptions containing a colon (e.g. client:foo, roundrobin:bar) on the /silenced/subscriptions/:subscription endpoint.
    • 🛠 Fixed a condition where processing check results with an invalid signature failed to complete. This often manifest as timeouts when waiting for sensu-server processes to terminate.

    🔄 Changes

    • 0️⃣ Default value for client settings has changed from nil to {}.

  • v0.26.1 Changes

    September 07, 2016

    🛠 Fixes

    • 🛠 Fixed a Sensu server settings bug that cause sensu-server to required a client definition in order to start.