Changelog

Releases

Enterprise 2.2.0 Release Notes

January 12, 2017 — Sensu Enterprise version 2.2.0 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • NEW: Added JIRA integration, create and resolve issues for Sensu events.

  • NEW: Added Rollbar integration, create and resolve messages/items for Sensu events.

  • NEW: The Slack integration now adds a “notification” field to attachments when one is provided in the event check definition.

  • IMPROVEMENT: Metric integration metric format mutation performance improvements.

  • IMPROVEMENT: Opsgenie integration now uses a different/improved HTTP client.

  • BUGFIX: Opsgenie integration now uses a string for alert tags, multiple tags are comma delimited.

Enterprise 2.1.0 Release Notes

November 17, 2016 — Sensu Enterprise version 2.1.0 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • NEW: ServiceNow Event Management support, create ServiceNow events for Sensu events.

Enterprise 2.0.0 Release Notes

October 25, 2016 — Sensu Enterprise version 2.0.0 has been released and is available for immediate download. Please note the following improvements:

IMPORTANT

This Enterprise release is built upon Sensu Core 0.26, which includes potentially breaking, backwards-incompatible changes. For more information, please refer to the Sensu Core 0.26.0 Important Changes.

CHANGES

Core 0.26.5 Release Notes

Source: GitHub.com

October 12, 2016 — Sensu Core version 0.26.5 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • BUGFIX: Fixed Sensu client configuration validation when the automatic per-client subscription is the client’s only subscription.

Core 0.26.4 Release Notes

Source: GitHub.com

October 5, 2016 — Sensu Core version 0.26.4 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • BUGFIX: Fixed in progress check extension execution tracking, the Sensu client now guards against multiple concurrent executions of the same check extension.

Core 0.26.3 Release Notes

Source: GitHub.com

September 23, 2016 — Sensu Core version 0.26.3 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • BUGFIX: Fixed a condition where /silenced API would fail to retrieve entries for subscriptions containing a mix of colons and hyphens, e.g. client:foo-bar-baz.

Core 0.26.2 Release Notes

Source: GitHub.com

September 21, 2016 — Sensu Core version 0.26.2 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • BUGFIX: Fixed a condition where events could not be successfully deleted when they originate from a client configured with a signature

  • BUGFIX: Fixed a condition where check results with an invalid signature would never complete processing. This often resulted in Sensu Server failing to shut down cleanly.

  • BUGFIX: Fixed a condition where /silenced API would fail to retrieve entries for subscriptions containing colons, e.g. client:foo.

  • BUGFIX: Made a change to ensure that new proxy clients are created with a per-client subscription just like regular clients.

Core 0.26.1 Release Notes

Source: GitHub.com

September 7, 2016 — Sensu Core version 0.26.1 has been released and is available for immediate download. Please note the following improvements:

CHANGES

  • BUGFIX: Fixed a condition where Sensu Server would fail to start without a client configuration definition.

Core 0.26.0 Release Notes

Source: GitHub.com

August 24, 2016 — Sensu Core version 0.26.0 has been released and is available for immediate download. Please note the following improvements:

IMPORTANT

This release includes potentially breaking, backwards-incompatible changes:

  • Event silencing is now built into Sensu Core, and a new /silenced API is now available. A new "handle_silenced": true attribute is available to opt-out of this new built-in silencing functionality on a per-handler basis.

  • Sensu Core version 0.26 requires Uchiwa version 0.18 or newer in order to make use of the new /silenced API feature. Prior versions of Uchiwa silence events using the “silence stashes” pattern, which will be honored by existing handlers until the now-deprecated event filtering is removed from a future version of sensu-plugin.

    NOTE: The new /silenced API and native event silencing features are intended to replace the “silence stash” pattern implemented in the sensu-plugin library and widely used by existing handlers. This “silence stashes” pattern is considered deprecated. Sensu 0.26 includes version 1.4.2 of the sensu-plugin library which continues to apply this pattern by default, but will log deprecation warnings as well. Set the check attribute enable_deprecated_filtering: false to disable the deprecated filtering behavior. Please refer to the Deprecating Event Filtering in sensu-plugin blog post for more information.

  • The handler definition subdue attribute is no longer supported. Time-based filtering is now supported by the new filter when attribute. Please update your handler definitions accordingly.

  • Check subdue definitions no longer support the "at": "handler" configuration setting.

CHANGES

  • NEW: Event silencing is now built into Sensu Core! The Sensu API now provides a set of /silenced endpoints, for silencing one or more checks and/or subscriptions (including the NEW client-specific subscriptions, below). Silencing applies to all event handlers by default, however a new handle_silenced handler definition attribute can be used to disable this functionality. Metric check events (OK) bypass event silencing.

    NOTE: this improvement is very closely related to the impending removal of event filtering in the sensu-plugin gem. See the recent Deprecating Event Filtering in sensu-plugin blog post for more information.

  • NEW: Every Sensu client now creates and subscribes to a unique client subscription (e.g. client:i-424242). Unique client subscriptions allow Sensu checks to target a single client (host) and enable silencing events for a single client. Fixes: #1327.

  • NEW: Introducing Subdue 2.0! Sensu subdue rules have a brand new configuration syntax, adding support for a broader number of applications, and subdue definitions are now supported by standalone checks.

    By way of comparison, the legacy subdue definition specification was limited to a single time window rule, with an array of exceptions. This was not only confusing, it made it very difficult to apply a simple “don’t execute this check outside of 9-5, M-F” rule.

    {
      "checks": {
        "example_check": {
          "command": "check_something.rb",
          "...": "...",
          "subdue": {
            "begin": "12:00:00 AM",
            "end": "11:59:00 PM",
            "days": ["monday", "tuesday", "wednesday", "thursday", "friday"],
            "exceptions": [
              {
                "begin": "9:00:00 AM",
                "end": "5:00:00 PM"
              }
            ]
          }
        }
      }
    }
    

    The new syntax is more verbose, but by doing away with the need for exceptions and adding support for defining an array of subdue time windows, it is much easier to configure.

    {
      "checks": {
        "example_check": {
          "command": "check_something.rb",
          "...": "...",
          "subdue": {
            "days": {
              "monday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "9:00:00 AM PST"
                },
                {
                  "begin": "5:00:00 PM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "tuesday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "9:00:00 AM PST"
                },
                {
                  "begin": "5:00:00 PM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "wednesday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "9:00:00 AM PST"
                },
                {
                  "begin": "5:00:00 PM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "thursday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "9:00:00 AM PST"
                },
                {
                  "begin": "5:00:00 PM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "friday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "9:00:00 AM PST"
                },
                {
                  "begin": "5:00:00 PM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "saturday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "11:59:59 PM PST"
                }
              ],
              "sunday": [
                {
                  "begin": "12:00:00 AM PST",
                  "end": "11:59:59 PM PST"
                }
              ]
            }
          }
        }
      }
    }
    

    NOTE: Subdue rules now apply to check publishing, ONLY (i.e. subdue definitions no longer support the "at": "handler" definition attribute, among other changes). Prior to this release, subdue rules could be provided via check definition subdue attribute (i.e. "at": "publisher") or the handler definition subdue attribute (i.e. "at": "handler"). Time-based filtering for handlers is now provided by Sensu filters (see below). Please refer to the new subdue reference documentation for more information. See: #1415.

  • NEW: Event filters now support time-based rules, via a new "when": {} filter definition attribute. The filter when specification uses the same syntax as the new Subdue 2.0 specification, simplifying time-based event filtering. Please refer to the filer when reference documentation for more information. *See #1415**.

  • NEW: Sensu Extensions can now be loaded from Rubygems and enabled/disabled via configuration! The sensu-install has also added support for installing Sensu Extensions (e.g. sensu-install -e system-profile). Extensions gems must be enabled via configuration, please refer to the Sensu extension reference documentation for more information. See: #1394.

  • NEW: A check can now be a member of more than one named aggregate, via a new check definition "aggregates": [] attribute. See: #1379; fixes #1342.

  • NEW: Added support for setting Redis Sentinel configuration via a new REDIS_SENTINEL_URLS environment variable. Please refer to the Sensu environment variables reference documentation for more information. **See #1411; fixes #1361.

  • NEW: Added support for automatically discovering and setting client name and address attributes (two of the few required attributes for a valid Sensu client definition). See: #1379; fixes #1362.

  • IMPROVEMENT: Added support for a new occurrences_watermark attribute, which is used by the built-in sensu-occurrences-extension filter to prevent sending resolve notifications for events that were not handled due to occurrence filtering. See: #1419 and #1427.

  • IMPROVEMENT: Only attempt to schedule standalone checks that have an interval. See: #1384; fixes #1286.

  • IMPROVEMENT: Locally configured standalone checks (e.g. on a Sensu server) are no longer accessible via the Sensu API /checks endpoint. See: #1417; fixes #1416.

  • IMPROVEMENT: Check TTL events are no longer created if the associated Sensu client has a current keepalive event. See #1428; fixes #861 and #1282.

  • IMPROVEMENT: Increased the maximum number of EventMachine timers from 100k to 200k, to accommodate very large Sensu installations that execute over 100k checks. See #1370; fixes #1368.

  • BUGFIX: Fixed a Sensu API /results endpoint race condition that caused incomplete response content. See #1372; fixes #1356.

Start your FREE trial today.

Already using Sensu Core? Upgrade to Sensu Enterprise today to take advantage of its enterprise console, added-value features, built-in integrations, FREE annual training, and enterprise-class support.