<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Cameron Johnston on Medium]]></title>
        <description><![CDATA[Stories by Cameron Johnston on Medium]]></description>
        <link>https://medium.com/@cwjohnston?source=rss-14fdc41b50d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*dNf__AdTomqC5B7-AZECQQ.jpeg</url>
            <title>Stories by Cameron Johnston on Medium</title>
            <link>https://medium.com/@cwjohnston?source=rss-14fdc41b50d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:41:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cwjohnston/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcement: Sensu Core repositories adding HTTPS, IPv6 and HTTP/2 support]]></title>
            <link>https://medium.com/the-sensu-blog/announcement-sensu-core-repositories-adding-https-ipv6-and-http-2-support-8480005b5ea4?source=rss-14fdc41b50d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8480005b5ea4</guid>
            <dc:creator><![CDATA[Cameron Johnston]]></dc:creator>
            <pubDate>Mon, 08 May 2017 14:31:01 GMT</pubDate>
            <atom:updated>2017-05-08T14:31:01.582Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Summary: On Wednesday, May 17th 2017, the Sensu Core repositories will be redirected to a new CDN distribution enabling SSL, IPv6 and HTTP/2 access methods. This upgrade should be transparent, requiring no changes for existing Sensu Core users.</strong></p><p>Thanks to the gracious and accommodating folks at <a href="https://www.fastly.com/">Fastly</a>, the Sensu Core package repositories at repositories.sensuapp.org will soon add support for HTTPS, IPv6 and HTTP/2 connections.</p><p>For some time now our friends at Fastly have donated their services, ensuring fast access to Sensu Core packages for users world-wide. In the last year Fastly has rolled out support for <a href="https://www.fastly.com/blog/ipv6-fastly">IPv6</a> and <a href="https://www.fastly.com/blog/http2-now-general-availability">HTTP/2</a> technologies. Thanks to Fastly, we’re ready to make these options available to Sensu Core users starting <strong>Wednesday, May 17th 2017. </strong>In addition, the new CDN configuration will support HTTPS connections to repositories.sensuapp.org using <a href="https://en.wikipedia.org/wiki/Server_Name_Indication">SNI</a>. <em>Note: most web browsers support HTTPS using SNI but some package managers do not.</em></p><p>To implement this change we’ll simply modify the DNS record for repositories.sensuapp.org to point to a new Fastly CDN hostname. Too easy, right? Should some unforeseen complications arise, we’ll have the option of falling back to the current CDN map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*qXgXsygQluPr-q1lJRex5w.gif" /></figure><p>The super helpful and friendly team at Fastly has already configured the new CDN map for us, and the feedback we’ve received from Sensu users who have manually reconfigured their infrastructure to test the new setup has been positive.</p><p>We’re excited for this upgrade and grateful to Fastly for their support! If you need help accelerating delivery of your content we wholeheartedly recommend their services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8480005b5ea4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/announcement-sensu-core-repositories-adding-https-ipv6-and-http-2-support-8480005b5ea4">Announcement: Sensu Core repositories adding HTTPS, IPv6 and HTTP/2 support</a> was originally published in <a href="https://medium.com/the-sensu-blog">The Sensu blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating to Sensu native silencing]]></title>
            <link>https://medium.com/the-sensu-blog/migrating-to-sensu-native-silencing-e7a322bab9da?source=rss-14fdc41b50d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7a322bab9da</guid>
            <dc:creator><![CDATA[Cameron Johnston]]></dc:creator>
            <pubDate>Mon, 10 Oct 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-04-17T22:00:39.080Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in September we released <a href="https://sensuapp.org/docs/0.26/overview/changelog.html">Sensu Core version 0.26</a>, adding silencing of clients and checks as a native construct in Sensu. In this post we aim to illuminate the specifics of this new approach to silencing and the possibilities it unlocks.</p><p>We call this new approach “native” because silencing of check results is now a concept built into Sensu Core itself. Prior to the release of Sensu Core 0.26, silencing check results — that is, preventing them from triggering a <a href="https://sensuapp.org/docs/0.26/reference/handlers.html">handler</a> — was dependent on the handler’s implementation.</p><p>Sensu handlers written in Ruby using the sensu-plugin library automatically took advantage of that library’s functionality for querying the API for a list of stashes under the /stashes/silenced path. Handlers written in other languages, or otherwise without using the sensu-plugin library either implemented their own code to query the /stashes API, or couldn’t be silenced in the same way.</p><p>This approach has been a source of confusion and consternation for many, as attempting to use a simple unix command like mailxfor handling messages can quickly turn into a yak-shaving exercise when silencing alerts from such a handler just doesn’t work in an intuitive way.</p><p>Even when using Ruby handlers with the sensu-plugin library in full effect, the /stashes implementation of silencing left something to be desired. For example, this approach does not make it possible to silence checks client subscription. In a highly-dynamic environment, new clients might be provisioned automatically, with client names not known in advance. Were this to happen during an incident, operators would have to silence new nodes as they come online to avoid alerting on incidends they have already otherwise silenced.</p><p>With the arrival of the /silenced API, scenarios like these become be a thing of the past.</p><p>The now-deprecated /stashes silencing implementation supports the following:</p><ol><li>Silencing all checks on a specific client</li><li>Silencing a specific check on a specific client</li><li>Silencing a specific check on all clients</li></ol><p>In comparison, the new native silencing implementation is more flexible, supporting:</p><ol><li>Silencing all checks on a specific client</li><li>Silencing a specific check on a specific client</li><li>Silencing all checks on clients with a specific subscription</li><li>Silencing a specific check on clients with a specific subscription</li><li>Silencing all checks on all clients</li><li>Automatically removing silencing when a check returns to OK status (via expire_on_resolve)</li></ol><p>For more detail on native silencing and the steps required to migrate from stash-based silencing, see our <a href="https://sensuapp.org/docs/latest/reference/silencing.html">Silencing reference documentation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7a322bab9da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/migrating-to-sensu-native-silencing-e7a322bab9da">Migrating to Sensu native silencing</a> was originally published in <a href="https://medium.com/the-sensu-blog">The Sensu blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deprecating Event Filtering in sensu-plugin]]></title>
            <link>https://medium.com/the-sensu-blog/deprecating-event-filtering-in-sensu-plugin-b60c7c500be3?source=rss-14fdc41b50d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b60c7c500be3</guid>
            <dc:creator><![CDATA[Cameron Johnston]]></dc:creator>
            <pubDate>Thu, 07 Jul 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-04-17T22:00:18.828Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are like many Sensu users, you’ve come to rely on <a href="https://sensuapp.org/docs/latest/reference/handlers.html">event handlers</a> from the <a href="https://sensu-plugins.io/">Sensu Plugins</a> project for sending notifications to on-call personnel. These handler plugins automatically apply filtering to reduce alert fatigue and improve the overall signal-to-noise ratio of notifications coming from Sensu. Historically this filtering logic has been implemented in the <a href="https://github.com/sensu-plugins/sensu-plugin">sensu-plugin framework</a>. This logic will soon be deprecated in the sensu-plugin library and move into the larger Sensu Core platform as first-class features. Read on to learn more about this important change.</p><h3>It was a good idea at the time…</h3><p>As a Sensu user, you may have already discovered that there’s a significant difference between using a Sensu Plugins handler and using more generic command line utilities to handle events. Configuring a handler definition which uses a command line utility like <a href="http://linux.die.net/man/1/mailx">mailx</a> to send email notifications will result in a message being sent for each received event, whereas a handler plugin like <a href="https://github.com/sensu-plugins/sensu-plugins-mailer/blob/1.0.0/bin/handler-mailer.rb">handler-mailer.rb</a> from the <a href="https://rubygems.org/gems/sensu-plugins-mailer">sensu-plugins-mailer</a> gem will generate far fewer messages.</p><p>The reason for this is that handlers from the Sensu Plugins project almost universally build on the <a href="https://github.com/sensu-plugins/sensu-plugin#handlers">Sensu::Handler class</a> provided by the sensu-plugin library. This class applies a series of filters to every event, evaluating whether the event is associated with a check that is silenced, has alerting disabled, or qualifies as an repeated event by way of <a href="https://github.com/sensu-plugins/sensu-plugin/blob/v1.3.0/lib/sensu-handler.rb#L119-L142">comparing </a><a href="https://github.com/sensu-plugins/sensu-plugin/blob/v1.3.0/lib/sensu-handler.rb#L119-L142">refresh and </a><a href="https://github.com/sensu-plugins/sensu-plugin/blob/v1.3.0/lib/sensu-handler.rb#L119-L142">occurrence attributes (a.k.a. occurrence filtering)</a>. The filters in this class are only available to Ruby plugins which use the sensu-plugin library, and even then there are some caveats.</p><p>When filtering was added to sensu-plugin circa 2011, abstracting this behavior into a shared library made sense. Native <a href="https://sensuapp.org/docs/latest/reference/filters.html">filters</a> as we know them now had not yet been added to Sensu, and since that time this common filtering behavior has helped handler authors avoid reimplementing the same filtering pattern in each handler.</p><h3>Expensive confusion</h3><p>Fast-forwarding to today, users are increasingly finding that filtering inside the handler plugin itself can be computationally expensive and may lead to unexpected alerting behaviors.</p><p>Ideally a Sensu event that will be filtered out should be dropped as early on in processing as possible. Forking a child process to perform event filtering inside the handler plugin requires more compute resources (CPU, RAM) than using a native Sensu filter. Wherever possible, forking a child process to execute a handler plugin should be avoided in order to keep resource usage low.</p><p>Without an understanding of sensu-plugin’s internals, it seems reasonable to assume that a handler configured with a set of native Sensu filters ought to notify the on-call operator if an event successfully navigates those filters. Unfortunately, due to aspects of sensu-plugin’s logic which cannot currently be overridden via configuration, the reality is that such events may be unexpectedly filtered. This has led users to open a number of issues (e.g. sensu <a href="https://github.com/sensu/sensu/issues/1067">#1067</a>, <a href="https://github.com/sensu/sensu/issues/1092">#1092</a>, <a href="https://github.com/sensu/sensu/issues/1097">#1097</a>, sensu-plugin <a href="https://github.com/sensu-plugins/sensu-plugin/issues/88">#88</a>) and pull requests (e.g. sensu-plugin <a href="https://github.com/sensu-plugins/sensu-plugin/pull/91">#91</a>, <a href="https://github.com/sensu-plugins/sensu-plugin/pull/107">#107</a>) around this sort of unexpected behavior.</p><p>For example, an event which has alerted on-call personnel may resolve itself without human intervention, but under the current occurrence filtering implementation resolution events can be unexpectedly filtered. The on-call personnel who would benefit from knowing the incident is resolved, allowing them to return to sleep, instead must manually review the state of alerts to determine that the event has been resolved.</p><p>These are just a few examples of the feedback we’ve received from Sensu users. There are almost certainly many more such issues already closed or simply unreported.</p><h3>So where do we go from here?</h3><p><strong><em>UPDATE</em>: Since this post was first published we’ve implemented many of the changes described herein. </strong><a href="https://sensuapp.org/blog/2016/07/07/sensu-plugin-filter-deprecation.html#september-2016-update"><strong>See our update below</strong></a><strong>.</strong></p><p>As stewards of Sensu we want to ensure success for users by providing functionality that is both obvious and consistent. The current situation leaves much to be desired in both of these criteria, and changing occurrence filtering logic will have a significant impact on how operators experience on-call rotations with Sensu. To remedy these issues we are planning to take the following actions over the coming weeks:</p><ul><li>Publish improved documentation around native Sensu filters, including examples which reproduce the current event filtering logic of sensu-plugin.</li><li>Release an open source <a href="https://github.com/sensu/sensu-extensions/issues/10">Sensu filter extension that reproduces sensu-plugin occurrence filtering logic</a></li><li>Publish a new minor version release of sensu-plugin (1.4.0) which:</li><li>Supports disabling the library’s built-in occurrence filtering on a per-check basis</li><li>Prints deprecation warnings in the Sensu log file when the built-in filtering is used</li><li>Update plugin gems published by the Sensu Plugins project to depend on sensu-plugin 1.4.0, once available</li><li>Subsequently, publish a new major version release of sensu-plugin (2.0.0) which disables occurrence filtering logic by default</li><li>Update plugin gems published by the Sensu Plugins project to depend on sensu-plugin 2.0.0, once available</li></ul><p>The current situation is such that we can’t move things forward without requiring some work from you, the Sensu operator. We need you to help us spread the word about this change by sharing this post with your friends and colleagues who use Sensu, and validate the documentation and software enhancements described above as they become available by adopting them into your Sensu environment. We believe that by making event filtering more configurable and decoupled from the sensu-plugin framework, native Sensu filters will become more effective for and better understood by all Sensu users — regardless of the executables they choose to use as handlers — which will be a win for our entire community.</p><h3>TL;DR</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/267/0*LfEc8hEq65K_8fXY.gif" /></figure><p>For the TL;DR crowd, here’s a condensed summary of the points laid out above:</p><ul><li>By default, handler plugins from the Sensu Plugins project filter events in a way which is relatively resource intensive, non-obvious and often confusing</li><li>Starting with the next minor release of the sensu-plugin library (1.4.0), this default event filtering will generate deprecation warnings in handler output which will be visible in the Sensu server log file</li><li>Documentation will be enhanced to illustrate how filtering currently implemented in sensu-plugin can be reproduced using native filters</li><li>To continue using the current occurrence filtering behavior beyond sensu-plugin 1.4.0, Sensu users will need to update their handler configurations to make use of new filter extensions and native filters</li><li>Future releases of Sensu will include enhancements (e.g. first-class silencing, occurrence filtering extension) to make this transition easier</li></ul><h3>Update: 6 September 2016</h3><p>Since this writeup was originally posted, we’ve been busy working on these and other improvements in preparation to release Sensu 0.26. This new release includes the following:</p><ul><li>New <a href="https://github.com/sensu-plugins/sensu-plugin/blob/master/CHANGELOG.md#v140---2016-07-20">sensu-plugin version 1.4,</a> which deprecates the library’s built-in filter behavior.</li><li>New <a href="https://sensuapp.org/docs/0.26/api/silenced-api.html">first-class silencing API</a>, enabling new approaches to silencing independent of sensu-plugin library.</li><li>New <a href="https://github.com/sensu-extensions/sensu-extensions-occurrences">occurrences filter extension</a>, an improved implementation of sensu-plugin’s now-deprecated occurrence filtering.</li><li><a href="https://sensuapp.org/docs/latest/reference/filters.html#filter-attribute-evaluation">Event filter documentation</a> now includes additional eval filter examples, among others.</li></ul><p>Although Sensu 0.26 will be the first release to include this new version of sensu-plugin, those who are interested can install the new version in an existing Sensu environment by running sudo /opt/sensu/embedded/bin/gem install sensu-plugin -v &#39;~&gt; 1.4&#39;.</p><p>With sensu-plugin 1.4.0 or later installed, deprecated filter behavior can be disabled on a per-check basis by setting the value of the enable_deprecated_filtering check attribute to false. The value of enable_deprecated_filtering defaults to true, meaning that sensu-plugin will continue to apply filtering as it has done in previous versions, but will print warnings when events are filtered by the now-deprecated code.</p><h3>Update: 14 April 2017</h3><p>With the <a href="http://sensuapp.com/docs/0.29/overview/changelog.html">Sensu 0.29 release</a> earlier this month we’ve continued to introduce changes to support this transition:</p><ul><li>sensu-plugin 1.4.5 has added support for globally disabling deprecated filtering methods. See <a href="https://github.com/sensu-plugins/sensu-plugin/tree/v1.4.5#important">the README</a> for details.</li><li>sensu-plugin 2.0.0 has been released. This version disables filtering methods by default. Most existing plugin projects will need updates to make use of sensu-plugin 2.0.</li><li>Sensu 0.29 includes sensu-plugin 1.4.5 for backward compatibility, and sensu-plugin 2.0.0 for use with future releases of existing plugin projects.</li><li>New <a href="https://github.com/sensu-extensions/sensu-extensions-check-dependencies">check dependencies filter extension</a> is also included in Sensu 0.29, implementing check dependency filtering method deprecated in sensu-plugin.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b60c7c500be3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/deprecating-event-filtering-in-sensu-plugin-b60c7c500be3">Deprecating Event Filtering in sensu-plugin</a> was originally published in <a href="https://medium.com/the-sensu-blog">The Sensu blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>