<?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 Sean Porter on Medium]]></title>
        <description><![CDATA[Stories by Sean Porter on Medium]]></description>
        <link>https://medium.com/@portertech?source=rss-5beea87f6f47------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4CU73d4Pd0Dq_8eeLBv8Fg.png</url>
            <title>Stories by Sean Porter on Medium</title>
            <link>https://medium.com/@portertech?source=rss-5beea87f6f47------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:26:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@portertech/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[The Road Ahead For Sensu]]></title>
            <link>https://medium.com/the-sensu-blog/the-road-ahead-for-sensu-ad1f4243e72b?source=rss-5beea87f6f47------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad1f4243e72b</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[sensus]]></category>
            <category><![CDATA[monitoringlove]]></category>
            <dc:creator><![CDATA[Sean Porter]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 16:27:03 GMT</pubDate>
            <atom:updated>2017-12-06T16:27:03.466Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in July, <a href="https://blog.sensuapp.org/sensu-core-version-1-0-is-now-available-c93b61977933">I proudly announced the release of Sensu Core 1.0</a> (<strong>a huge milestone!</strong>) and provided a list of major features and assets to be developed in Q3 and Q4 of 2017. The list included Check Hooks, Scheduled Maintenance, and official 1.x Docker images. Since then, there have been two significant releases of Sensu Core, containing bug fixes and <strong>many rad features</strong>!</p><h4>Sensu Core 1.1 (2017–09–27)</h4><ul><li>Check Hooks — event enrichment and auto-remediation!</li><li>Check STDIN data — for data driven plugins</li><li>Splayed proxy check request publishing</li><li>Improved check TTL monitoring performance</li><li><a href="https://github.com/sensu/sensu/blob/master/CHANGELOG.md#110---2017-09-27">Read the full CHANGELOG</a></li></ul><h4>Sensu Core 1.2 (2017–12–05)</h4><ul><li>Scheduled Maintenance — silencing at a predetermined start time</li><li>Global client keepalive configuration!</li><li><a href="https://github.com/sensu/sensu/blob/master/CHANGELOG.md#120---2017-12-05">Read the full CHANGELOG</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mzXKtwGOY2elMyGUxn48bA.jpeg" /><figcaption>Party on Wayne, party on Garth.</figcaption></figure><h3>Some Fun Facts!</h3><p>The Sensu 1.x software repositories serve up an average of 12TB of data per month, that’s approximately 13333 installs a day! Keep in mind these numbers do not include public and private mirrors nor do they include Docker container images! Seeing the scale of Sensu adoption excites me greatly, it’s one of the greatest sources of motivation for many working on Sensu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*eEMYuNUSMasANoufhMRxLw.png" /></figure><h3>What’s next for 1.x?</h3><p>With the release of Sensu Core 1.2, the features listed in my <a href="https://blog.sensuapp.org/sensu-core-version-1-0-is-now-available-c93b61977933">July post</a> (e.g. Check Hooks) have shipped and been put to good use by many! One final task remains for Q4 of 2017, publishing official Sensu 1.x Docker images, happy holidays! Going forward, with the development of Sensu 2.0 in full swing, 1.x development efforts will be focused on minor features, bug fixes, and security patches. New features will be implemented in Sensu 2.0, including those currently not possible with Sensu 1.x! Commercial support for Sensu 1.x will continue until 2020.</p><blockquote>Going forward, with the development of Sensu 2.0 in full swing, 1.x development efforts will be focused on minor features, bug fixes, and security patches.</blockquote><h3>Sensu 2.x</h3><p>Back in August, at the <a href="https://sensuapp.org/summit">inaugural Sensu Summit</a>, I had the pleasure of announcing the development of the next generation of Sensu. Sensu 2.0 is a complete rewrite in <a href="https://golang.org/">Go</a> which greatly reduces Sensu’s operational overhead, making it much easier to operate with fewer moving parts. At the Summit, we launched the <a href="https://sensuapp.org/alpha">Sensu 2.0 Private Alpha Program</a>, a small, high-touch engagement to collaborate with the Sensu engineering team as they produce a Beta ready for wider use. Over the past few months, Alpha Program participants have provided invaluable feedback and bug reports (<strong>THANK YOU!</strong>), and the engineering team has been working at a rapid pace! It’s not too late to get involved with the Alpha Program (<a href="https://sensuapp.org/alpha">sign up here</a>). The Alpha Program will continue until early Q1 of 2018, right up until the Sensu 2.0 Beta release!</p><h3>What’s next for 2.x?</h3><p>The Sensu 2.0 Beta release is planned for Q1 of 2018 (February). The Beta is still an early release of 2.0 (with 1.x feature parity), intended for wide use, allowing anyone to experiment with and test the next generation of Sensu. It is at this time that the related software repositories will become public, opening the doors for community contributors! Sensu 2.0 will remain in Beta until the end of Q3, giving the Sensu Community time to become familiar with the technology. Throughout the Beta period, Sensu Inc. will be feverishly creating 2.0 documentation, training, and support resources. Until these resources are available, commercial training and support will not be available for Sensu 2.0 (1.x training and support will be available). The Beta period also creates a great opportunity for Sensu Community projects to adjust course for Sensu 2.0 if necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*L97vfUdKhYUs0YEAN-QFjQ.jpeg" /><figcaption>I CAN BARELY CONTAIN MY EXCITEMENT!!!</figcaption></figure><h3>The 2018 Timeline</h3><p>The following is a high-level timeline for 2018, providing an idea of what you can expect from Team Sensu this coming year. This timeline only scratches the surface; 2018 is going to be an incredible year for Sensu and its ever growing community of passionate people!</p><h4>Q1 — Sensu 2.0 Beta</h4><ul><li>Sensu 1.x feature parity</li></ul><h4>Q3 — Sensu 2.0 Beta Dashboard</h4><ul><li>Uchiwa 1.x feature parity</li></ul><h4>Q4 — Sensu 2.0</h4><ul><li>Commercial Support &amp; Training</li><li>Enterprise Features</li></ul><h3>Full Steam Ahead!</h3><p>The Sensu project has now been around for over <strong>SIX YEARS!</strong> At its inception, Sensu solved many of the monitoring problems introduced by a significant paradigm shift in infrastructure delivery (i.e. cloud and automation). Sensu took what was known to work (i.e. service checks) and provided an architecture and monitoring framework designed for a new age in infrastructure. Being open source has enabled Sensu adoption well beyond what I could have dreamt of in 2011 and this has fostered a wonderful community full of passionate and helpful people. The Sensu community has propelled the project forward, creating an entire ecosystem of tools and resources around Sensu, while also helping drive Core feature development. Together, we have built Sensu 1.x, a powerful monitoring tool for today’s infrastructure.</p><p>Today, we are all experiencing another paradigm shift in infrastructure and software delivery: containerization. Containers, while extremely useful, introduce new monitoring challenges and workflows. Sensu 2.0 tackles these new challenges and intends to fit into the emerging workflows around containers. While Sensu 2.0 is positioned for the future, it makes no compromises in terms of what you can do with Sensu 1.x. Sensu 2.0 aims to monitor from the server closet to the containerized cloud. I am very excited to see what people do with Sensu 2.0, 2018 is going to be an incredible year! Be sure to get involved in the <a href="https://sensuapp.org/alpha">Sensu 2.0 Private Alpha</a> (if you haven’t already) and keep an eye out for the Beta in Q1!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/1*ya5Zb0cQZu-LWOkHT20PJA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad1f4243e72b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/the-road-ahead-for-sensu-ad1f4243e72b">The Road Ahead For Sensu</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[Using Check Hooks]]></title>
            <link>https://medium.com/the-sensu-blog/using-check-hooks-a739a362961f?source=rss-5beea87f6f47------2</link>
            <guid isPermaLink="false">https://medium.com/p/a739a362961f</guid>
            <category><![CDATA[sensus]]></category>
            <category><![CDATA[monitoringlove]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Sean Porter]]></dc:creator>
            <pubDate>Wed, 18 Oct 2017 16:04:35 GMT</pubDate>
            <atom:updated>2017-10-18T16:04:35.222Z</atom:updated>
            <content:encoded><![CDATA[<p>Team Sensu recently released Sensu Core 1.1, which includes a powerful new feature called <a href="https://sensuapp.org/docs/latest/reference/checks.html#check-hooks">Check Hooks</a>. Check Hooks are commands run by the Sensu client in response to the result of check command execution. Check Hooks allow Sensu users to automate actions routinely performed by operators in response to monitoring alerts, freeing precious operator time to be used elsewhere and to greater effect!</p><h3>Why Check Hooks?</h3><p>The practice of using Sensu for auto-remediation tasks and automated data gathering for incident triage continues to gain traction amongst Sensu users. Although these practices were achievable with previous Sensu releases, Sensu did not make it easy, as all actions had to be orchestrated by a Sensu server. <a href="https://twitter.com/nstielau">Nick Stielau</a> wrote a <a href="http://dev.nuclearrooster.com/2013/07/27/remediation-with-sensu/">great blog post</a> about auto-remediation with Sensu back in 2013! Now, these practices are more simple and straightforward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*ndOSe5hdezUnqvDbXrPz6g.gif" /></figure><h3>Check Hook Configuration</h3><p>Check Hooks have names that associate them with one or more <a href="https://sensuapp.org/docs/latest/reference/checks.html#sensu-check-specification">Sensu check status codes</a> (e.g. 1) or severities (e.g. “critical”). Valid Hook names include (in order of precedence) “1”-”255&quot;, “ok”, “warning”, “critical”, “unknown”, and “non-zero”. Following a check command execution, the Sensu client will execute the appropriate configured Hook command, depending on the <a href="https://sensuapp.org/docs/latest/reference/checks.html#sensu-check-specification">check execution status</a> (e.g. 1). A Check Hook must have a configured command to execute and can have an execution timeout (default is 60s). Optionally, a Hook command can expect and consume JSON serialized Sensu client and check data via STDIN.</p><p>The following example Check Hook (“non-zero”) captures the system process tree if the check command returns a non-zero status (e.g. 2), indicating that the Nginx process is unhealthy.</p><pre>{<br>  &quot;checks&quot;: {<br>    &quot;nginx_process&quot;: {<br>      &quot;command&quot;: &quot;check-process.rb -p nginx&quot;,<br>      &quot;subscribers&quot;: [&quot;proxy&quot;],<br>      &quot;interval&quot;: 30,<br>      <strong>&quot;hooks&quot;: {<br>        &quot;non-zero&quot;: {<br>          &quot;command&quot;: &quot;ps aux&quot;,<br>          &quot;timeout&quot;: 10<br>        }<br>      }</strong><br>    }<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*VEUUAdUsDdL-nuV1KFfVPA.gif" /></figure><h3>More Examples</h3><p>Check Hook commands support <a href="https://sensuapp.org/docs/latest/reference/checks.html#check-token-substitution">check token substitution</a>, just like check commands! The following example will capture disk utilization information for the database disk. The Sensu client definition custom attributes, e.g. db.disk.mount, are used to allow Sensu client specific values for the database disk mount point and alert thresholds. If a Sensu client definition does not have a db.* custom attribute, the <a href="https://sensuapp.org/docs/latest/reference/checks.html#token-substitution-default-values">declared default value</a> is used, e.g. / .</p><pre>{<br>  &quot;checks&quot;: {<br>    &quot;db_disk_usage&quot;: {<br>      &quot;command&quot;: &quot;check-disk-usage.rb -I :::db.disk.mount|/::: -w :::db.disk.warn|90::: -c :::db.disk.warn|95:::&quot;,<br>      &quot;subscribers&quot;: [&quot;linux&quot;],<br>      &quot;interval&quot;: 30,<br>      <strong>&quot;hooks&quot;: {<br>        &quot;non-zero&quot;: {<br>          &quot;command&quot;: &quot;df -h :::db.disk.mount|/:::&quot;,<br>          &quot;timeout&quot;: 10<br>        }<br>      }</strong><br>    }<br>  }<br>}</pre><p>As mentioned previously, Check Hooks can be used for rudimentary auto-remediation tasks, such as (re)starting a process. The following example will start Nginx if the check command execution returns a status of 2 (critical, not running). If the check command execution returns any other non-zero status, the process tree will be captured, assisting operators by providing additional context. This example could be used on systems that lack proper service management.</p><blockquote>“This example effectively replaces Monit.” — <a href="https://twitter.com/amdprophet">Justin Kolberg</a></blockquote><pre>{<br>  &quot;checks&quot;: {<br>    &quot;nginx_process&quot;: {<br>      &quot;command”: &quot;check-process.rb -p nginx&quot;,<br>      &quot;subscribers&quot;: [&quot;proxy&quot;],<br>      &quot;interval&quot;: 30,<br>      <strong>&quot;hooks&quot;: {<br>        &quot;critical&quot;: {<br>          &quot;command&quot;: &quot;sudo /etc/init.d/nginx start&quot;,<br>          &quot;timeout&quot;: 30<br>        },<br>        &quot;non-zero&quot;: {<br>          &quot;command&quot;: &quot;ps aux&quot;,<br>          &quot;timeout&quot;: 10<br>        }<br>      }<br>    </strong>}<br>  }<br>}</pre><p>Check Hook commands can optionally receive JSON serialized Sensu client and check data passed via STDIN. This functionality allows Hook commands (scripts) to take different actions depending on the data they receive. I am excited to see what the Sensu community does with this! The following example will execute a custom Hook command when the local HTTP API is determined to be unhealthy.</p><pre>{<br>  &quot;checks&quot;: {<br>    &quot;api_health&quot;: {<br>      &quot;command”: &quot;check-http.rb -u http://localhost:8080/healthz&quot;,<br>      &quot;subscribers&quot;: [&quot;api&quot;],<br>      &quot;interval&quot;: 20,<br><strong>      &quot;hooks&quot;: {<br>        &quot;non-zero&quot;: {<br>          &quot;command&quot;: &quot;custom-script.py&quot;,<br>          &quot;stdin&quot;: true,<br>          &quot;timeout&quot;: 10<br>        }<br>      }<br>    </strong>}<br>  }<br>}</pre><p><strong>NOTE:</strong> Because the Hook attribute stdin is set to true, the command script custom-script.py must expect the JSON data via STDIN, read it, and close STDIN, or its execution will hang until the timeout terminates it.</p><h3>When Not To Use Them</h3><p>So often when we are given a new tool or feature, it becomes our new hammer, and everything around us starts to look like a nail. Check Hooks are powerful, with many applications, however, it’s important to acknowledge their limitations.</p><p>Check Hooks are not Sensu Event Handlers. As Hooks are executed by the Sensu client, their local data is limited compared to the data available to a Sensu server. For example, the Sensu client is not aware of the check’s execution history, whether its status is flapping, the number of state occurrences, <strong>or if the check is silenced</strong>. I do not recommend using Hooks for alerting purposes due to the lack of this data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pMwcyrolQ_Spa68TMO8xCg.gif" /></figure><p>Check Hooks are also not for complex auto-remediation tasks. While Hooks are more than capable of executing single step remediation tasks, they lack any sort of built-in rules or workflow engine, which would enable multi-step or multi-stage tasks with conditional logic. If you must do complex auto-remediation tasks, I recommend you take a look at <a href="https://stackstorm.com/">StackStorm</a>, they even have a <a href="https://github.com/StackStorm/st2contrib/tree/master/packs/sensu">Sensu integration pack</a>!</p><h3>Give Check Hooks A Try!</h3><p>I hope this post helped you learn what Sensu Check Hooks are and has you excited about them! I suspect that you already have Hook ideas of your own, ideas that are probably much better than the examples above. <a href="https://sensuapp.org/docs/1.1/installation/upgrading.html#upgrading-sensu">Upgrade your Sensu installations to 1.1</a> and give Hooks a whirl! Share your Hook ideas in the <a href="http://slack.sensu.io/">Sensu Community Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a739a362961f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/using-check-hooks-a739a362961f">Using Check Hooks</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[The Sensu Prometheus Collector]]></title>
            <link>https://medium.com/the-sensu-blog/the-sensu-prometheus-collector-972c441d45e?source=rss-5beea87f6f47------2</link>
            <guid isPermaLink="false">https://medium.com/p/972c441d45e</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[monitoringlove]]></category>
            <category><![CDATA[prometheus]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[sensus]]></category>
            <dc:creator><![CDATA[Sean Porter]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 18:01:00 GMT</pubDate>
            <atom:updated>2017-10-04T18:01:00.678Z</atom:updated>
            <content:encoded><![CDATA[<p>I am very excited to share with you a little project that I started on Monday, the <a href="https://github.com/portertech/sensu-prometheus-collector#sensu-prometheus-collector">Sensu Prometheus Collector</a>! I have wanted to create something like this for a long time now and I finally found the time to do it.</p><p>The Sensu Prometheus Collector is a <a href="https://sensuapp.org/docs/1.0/reference/plugins.html#what-is-a-sensu-plugin">Sensu Check Plugin</a> that collects metrics from a Prometheus <a href="https://prometheus.io/docs/instrumenting/exporters/">exporter</a>, <a href="https://prometheus.io/docs/instrumenting/clientlibs/">metric HTTP endpoint</a>, or the <a href="https://prometheus.io/docs/querying/api/">HTTP Query API</a>. The collected metrics are outputted to STDOUT in one of three formats: Influx (the default), Graphite, or JSON. Sensu can then deliver the outputted/collected metrics to one or more time-series databases, like InfluxDB or Graphite! <strong>Choose your TSDB</strong>!</p><h3>How Sensu Complements Prometheus</h3><p>The Sensu Prometheus Collector turns Sensu into a <strong>SUPER POWERED Prometheus metric poller</strong>, leveraging Sensu’s PubSub design and client auto-registration. Sensu is able to automatically discover and begin polling metric HTTP endpoints, securely transporting collected metrics to a desired time-series database. Sensu’s client connections traverse complex network topologies, including those that use NAT and VPNs, eliminating any need to punch holes in firewalls for metric scraping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*xgVmkHvUmvRy2GUbCv-rZw.gif" /><figcaption>Connecting projects with Sensu makes me this happy</figcaption></figure><h3>Usage Examples</h3><p>Operating the Sensu Prometheus Collector is very straightforward and configuring a Sensu Check to run it is easy. Simply poll metrics from a Prometheus exporter or an application’s metric HTTP endpoint and output them in the Influx Line Protocol format:</p><pre>$ sensu-prometheus-collector -exporter-url \ <a href="http://localhost:8080/metrics">http://localhost:8080/metrics</a><br>go_memstats_last_gc_time_seconds value=0 1506991233<br>go_memstats_mspan_sys_bytes value=32768 1506991233<br>...</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0uYoJqxJfUjB8b6cIw9fUw.gif" /><figcaption>Now we’re cooking up some</figcaption></figure><h3>Sensu Configuration Examples</h3><p>A Sensu Check named “prometheus_metrics”, that collects metrics from a metric HTTP endpoint on application tier systems, and sends them to a Sensu Event Handler named “influx”:</p><pre>{<br>  &quot;checks&quot;: {<br>    &quot;prometheus_metrics&quot;: {<br>      &quot;type&quot;: &quot;metric&quot;,<br>      &quot;command&quot;: &quot;sensu-prometheus-collector -exporter-url http://localhost:8080/metrics&quot;,<br>      &quot;subscribers&quot;: [&quot;app_tier&quot;],<br>      &quot;interval&quot;: 10,<br>      &quot;handler&quot;: &quot;influx&quot;<br>    }<br>  }<br>}</pre><p>A Sensu Event Handler named “influx”, that sends collected metrics in the Influx Line Protocol format to a Influx UDP listener:</p><pre>{<br>  &quot;handlers&quot;: {<br>    &quot;influx&quot;: {<br>      &quot;type&quot;: &quot;udp&quot;,<br>      &quot;mutator&quot;: &quot;only_check_output&quot;,<br>      &quot;socket&quot;: {<br>        &quot;host&quot;: &quot;influx.example.com&quot;,<br>        &quot;port&quot;: 8189<br>      }<br>    }<br>  }<br>}</pre><p>Hopefully these examples helped you get an idea of how the Sensu Prometheus Collector works and how to configure Sensu to use it.</p><p>The full power of the Sensu Prometheus Collector can be found in the help output:</p><pre>$ sensu-prometheus-collector -h<br>Usage of ./sensu-prometheus-collector:<br> -exporter-url string<br> Prometheus exporter URL to pull metrics from.<br> -metric-prefix string<br> Metric name prefix, only supported by line protocol output formats.<br> -output-format string<br> The check output format to use for metrics {influx|graphite|json}. (default “influx”)<br> -prom-query string<br> Prometheus API query string. (default “up”)<br> -prom-url string<br> Prometheus API URL. (default “http://localhost:9090”)</pre><p>For more examples and documentation, please check out the project’s <a href="https://github.com/portertech/sensu-prometheus-collector/blob/master/README.md">README</a>.</p><h3>Contributing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*PD90BluQsMFhHGkpCUtYnw.jpeg" /></figure><p>The Sensu Prometheus Collector is very new (and raw), making for many opportunities to contribute to the project! I have begun to create <a href="https://github.com/portertech/sensu-prometheus-collector/issues">GitHub issues</a> for desirable features and enhancements, labeling some of them with “<a href="https://github.com/portertech/sensu-prometheus-collector/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22">good first issue</a>” to help identify issues that are more approachable. I hope you find this little project as exciting as I do, help me improve it and give it the polish that it deserves!</p><h3>Try It!</h3><p>The Sensu Prometheus Collector is rad and ready for you to try! Use <a href="https://prometheus.io/docs/instrumenting/exporters/">Prometheus instrumentation libraries and exporters</a> with Sensu and store the collected metrics in your favourite time-series database. The more of us using the plugin and experimenting, the better!</p><p>The Sensu Prometheus Collector can be <a href="https://github.com/portertech/sensu-prometheus-collector">found on my GitHub</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*pFc7KgC_XGCGmLrtWW6x2w.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972c441d45e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/the-sensu-prometheus-collector-972c441d45e">The Sensu Prometheus Collector</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[Sensu Core version 1.0 is now available!]]></title>
            <link>https://medium.com/the-sensu-blog/sensu-core-version-1-0-is-now-available-c93b61977933?source=rss-5beea87f6f47------2</link>
            <guid isPermaLink="false">https://medium.com/p/c93b61977933</guid>
            <category><![CDATA[release-notes]]></category>
            <category><![CDATA[releases]]></category>
            <category><![CDATA[monitoringlove]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Sean Porter]]></dc:creator>
            <pubDate>Tue, 11 Jul 2017 23:56:12 GMT</pubDate>
            <atom:updated>2017-07-12T00:58:04.855Z</atom:updated>
            <content:encoded><![CDATA[<p>I am thrilled to announce the general release of <a href="https://sensuapp.org/docs/1.0/overview/changelog.html">Sensu Core version 1.0</a>, which is now available to <a href="https://sensuapp.org/downloads">download and install</a>.</p><p>This release represents a significant milestone for Sensu. <a href="https://blog.sensuapp.org/five-years-of-sensu-94789997a56b">The journey</a> <a href="https://blog.sensuapp.org/from-open-source-to-open-core-bc3007c96236">from a small side project</a> to <a href="https://blog.sensuapp.org/introducing-sensu-inc-9f1d2027c577">having a full-fledged company behind it</a> has been incredible. Today, where Sensu has thousands of users and many customers, it is fun to look back at the <a href="https://github.com/sensu/sensu/blob/master/CHANGELOG.md#097---2012-09-20">early changelog</a> to remember just how far we have come. This 1.0 release is a recognition that Sensu’s monitoring primitives have matured and that it has a stable set of features and APIs that users have come to depend on to solve their unique monitoring challenges.</p><h3><strong>What’s New?</strong></h3><p>Sensu 1.0 is a rerelease of <a href="https://sensuapp.org/docs/0.29/overview/changelog.html">version 0.29</a> under the covers (with a few minor bug fixes and features), but comes with a promise of adhering to Semantic Versioning (a.k.a <a href="http://semver.org/">SemVer</a>) going forward (thanks again for <a href="https://github.com/sensu/sensu/issues/1448">suggesting we do</a> @spang).</p><p>That said, I know many Sensu users (especially long-time users) are still running older versions of Sensu, and we have shipped a significant number of features and enhancements in the last 12–15 months, so I want to take this opportunity to highlight some of the major improvements we’ve implemented on our path to this important milestone:</p><p><strong>Sensu Core version 0.23 (April 2016):</strong></p><ul><li>Native <a href="https://sensuapp.org/docs/latest/reference/redis.html#redis-sentinel-configuration">Redis Sentinel support</a> (for <a href="https://sensuapp.org/docs/latest/reference/redis.html#redis-high-availability-configuration">high availability configurations</a>)</li><li><a href="https://sensuapp.org/docs/latest/reference/configuration.html#sensu-command-line-interfaces-and-arguments">print_config CLI option</a> (for troubleshooting configuration issues)</li><li><a href="https://sensuapp.org/docs/latest/reference/filters.html#filter-attribute-eval-tokens">Filter attribute token substitution</a></li><li>AIX packages</li></ul><p><strong>Sensu Core version 0.24 (June 2016):</strong></p><ul><li><a href="https://sensuapp.org/docs/latest/reference/aggregates.html">Named Aggregates</a></li><li>validate_config CLI option (for validating configuration before restarting)</li><li><a href="https://sensuapp.org/docs/latest/api/clients-api.html#clients-post">POST /clients API endpoint</a> (for proxy client management)</li><li><a href="https://sensuapp.org/docs/latest/reference/events.html#event-attributes">Persistent event IDs</a></li></ul><p><strong>Sensu Core version 0.25 (June 2016):</strong></p><ul><li><a href="https://sensuapp.org/docs/latest/reference/clients.html#deregistration-attributes">Client Deregistration</a> Events</li><li>API performance improvements</li></ul><p><strong>Sensu Core version 0.26 (August 2016):</strong></p><ul><li><a href="https://sensuapp.org/docs/latest/reference/silencing.html">Native Event Silencing</a> and <a href="https://sensuapp.org/docs/latest/api/silenced-api.html">/silenced API</a>!</li><li>Redesigned <a href="https://sensuapp.org/docs/latest/reference/checks.html#subdue-attributes">Check Subdue</a></li><li>Automated <a href="https://sensuapp.org/docs/latest/reference/clients.html#client-attributes">Client “name” and “address” attribute</a> discovery</li><li>New <a href="https://sensuapp.org/docs/latest/reference/filters.html#when-attributes">Filter “when” attribute</a> (only apply a filter for a time window)</li><li>Support for <a href="https://sensuapp.org/docs/latest/reference/extensions.html#use-sensu-install-to-install-sensu-extensions">loading Sensu extensions from Ruby gems</a></li></ul><p><strong>Sensu Core version 0.27 (January 2017):</strong></p><ul><li>Sensu Client <a href="https://sensuapp.org/docs/latest/reference/clients.html#http-socket">HTTP input socket</a></li><li>Per platform/release/architecture packaging with support for native service managers (e.g. systemd)</li></ul><p><strong>Sensu Core version 0.28 (February 2017):</strong></p><ul><li><a href="https://sensuapp.org/docs/latest/reference/checks.html#proxy-requests-attributes">Proxy Check Requests</a></li><li>Optional <a href="https://sensuapp.org/docs/latest/reference/checks.html#check-attributes">Cron syntax for check execution scheduling</a></li><li><a href="https://sensuapp.org/docs/latest/api/health-and-info-api.html#the-info-api-endpoint">Sensu Server Registry</a></li></ul><p><strong>Sensu Core version 0.29 (April 2017):</strong></p><ul><li>Built-in “occurrences” and “check_dependencies” filters</li><li>Sensu Server Tasks (replacing Sensu Server Leader Election, can now distribute the Leader responsibilities amongst one or more Sensu Servers in an installation)</li><li><a href="https://github.com/sensu/sensu/pull/1595">API response content filtering</a>!</li><li>Sensu Settings Hexdigest (used to compare running configurations)</li></ul><h3><strong>What’s Next?</strong></h3><p>Sensu Core has several exciting new features and enhancements on the 1.x roadmap!</p><p><strong>Scheduled maintenance.</strong> Sensu currently gives users the ability to silence a check and/or client subscriptions, stopping related Sensu events from being handled (e.g. no notifications). We plan to add the ability to silence a check and/or client subscriptions at a predetermined start time, with an optional end time, enabling users to silence events for scheduled maintenance windows in advance.</p><p><strong>Check hooks.</strong> The Sensu client’s primary function is to execute check commands and publish their results for processing, allowing a Sensu server to take the appropriate actions. The practice of using Sensu for auto-remediation tasks and automated data gathering for incident triage continue to gain traction amongst Sensu users. Although these practices are achievable, Sensu does not currently make it easy, as all actions must be orchestrated by a Sensu server. We plan to introduce check hooks, commands run by the Sensu client in response to the result of the check command execution.</p><p><strong>Official Docker images.</strong> We plan to publish official Docker images for Sensu’s components, as well as guidelines for deploying Sensu in a containerized environment.</p><h3><strong>Upgrade to Sensu 1.0</strong></h3><p>I am ecstatic about the Sensu Core 1.0 release and the coming features, and I hope you are too! Although Sensu Core version 1.0 is ready to go, we are actively testing Sensu plugins to ensure they work with the release (<a href="https://github.com/sensu-plugins/sensu-plugins-feature-requests/issues/27">you can help too!</a>). Please be sure to give the <a href="https://github.com/sensu/sensu/blob/master/CHANGELOG.md">Sensu Core CHANGELOG</a> a close look before upgrading. Users on a release prior to 0.27 must give the <a href="https://blog.sensuapp.org/sensu-core-version-0-27-is-now-available-b9689647ba3c">0.27 release notes</a> a close inspection, as the 0.27 release introduced changes to the Sensu repositories, packages, and the means of service management (e.g. systemd). <a href="https://sensuapp.org/support">Support is here</a> should you run into any problems along the way.</p><h3><strong>And Thank You!</strong></h3><p>Sensu would not be what it is today without our incredible community. Thanks to past maintainers like <a href="https://twitter.com/CaffeinatedEng">Matt Jones</a> and<a href="https://twitter.com/CaffeinatedEng"><strong> </strong></a><a href="https://github.com/tas50">Tim Smith</a> along with newer contributors (looking at you <a href="https://github.com/luisdavim">Luis Davim</a>, <a href="https://github.com/evesy">Mike Eves</a> and <a href="https://github.com/smbambling">Steven Bambling</a>). A very special thank you to <a href="https://github.com/eheydrick">Eric Heydrick</a> for his long commitment as a maintainer to Sensu plugins and also to <a href="https://github.com/majormoses">Ben Abrams</a> for all his work as our latest maintainer. We are thankful for all of your contributions and to the many others who have contributed over the years ❤️.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c93b61977933" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/sensu-core-version-1-0-is-now-available-c93b61977933">Sensu Core version 1.0 is now available!</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[Five Years of Sensu]]></title>
            <link>https://medium.com/the-sensu-blog/five-years-of-sensu-94789997a56b?source=rss-5beea87f6f47------2</link>
            <guid isPermaLink="false">https://medium.com/p/94789997a56b</guid>
            <dc:creator><![CDATA[Sean Porter]]></dc:creator>
            <pubDate>Tue, 12 Jul 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-12T19:27:49.622Z</atom:updated>
            <content:encoded><![CDATA[<p>Although Sensu wouldn’t become a <a href="http://portertech.ca/2011/11/01/sensu-a-monitoring-framework/">publicly available open-source project</a> until November 2011, <strong>the Sensu journey officially began five years ago this week</strong>. Five years ago I committed <a href="https://github.com/sensu/sensu/commit/7bb7f2887f8677cd51e74e23b6ad96be5f47e8b3">an empty README.md file</a> (commit #1) to an otherwise empty repository called “Sensu” where I would then <a href="https://github.com/sensu/sensu/commit/c5c8071bb37fcf359606bced92035e3f4ac1e0f3">describe my #monitoringlove goals</a> (commit #2), and the rest is history. We started this humble project at <a href="http://www.sonian.com/">Sonian</a> to replace an aging Nagios installation that couldn’t keep up with the rapidly evolving demands of a dynamic public-cloud infrastructure. Sonian was not (and is not) the only company facing that challenge, which has resulted in Sensu’s continued growth, and establishment as one of the most trusted monitoring platforms in the world today.</p><h3>Five years by the numbers</h3><p>Digging through the commit data we could extract from the relevant GitHub.com APIs, a few numbers stand out. In the <strong>1826 days </strong>since committing an empty README.md file to an empty repo there have been:</p><ul><li><strong>over 20000 commits</strong></li><li>contributions from <strong>over 300 developers</strong> (from <strong>dozens of countries in five continents</strong> around the world)</li><li><strong>over 1500 issues closed</strong></li><li><strong>$0 in venture (or any other) capital funding</strong> raised</li><li>a whole lot of <a href="https://twitter.com/hashtag/monitoringlove">#monitoringlove</a> shared</li></ul><p>Although only roughly 20–30% of these commits contain geotagged location data, it is exciting to see that subset of contributions visualized on an interactive map as evidence that Sensu has truly spread the <strong>#monitoringlove</strong> to a global community!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fzerosixzero.carto.com%2Fviz%2F579484be-49a5-4e59-8543-e635ad1b6288%2Fembed_map&amp;url=https%3A%2F%2Fzerosixzero.carto.com%2Fviz%2F579484be-49a5-4e59-8543-e635ad1b6288%2Fpublic_map&amp;image=https%3A%2F%2Fcartocdn-ashbu.global.ssl.fastly.net%2Fzerosixzero%2Fapi%2Fv1%2Fmap%2Fstatic%2Fnamed%2Ftpl_579484be_49a5_4e59_8543_e635ad1b6288%2F1200%2F630.png&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=carto" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/c88e13330517d3ed929661cc656b7ef3/href">https://medium.com/media/c88e13330517d3ed929661cc656b7ef3/href</a></iframe><blockquote><strong>NOTE</strong>: the map plots commits made to the open-source Sensu Core code base and Sensu Plugins projects only. It does not include commits made to the various community dashboard projects, or the roughly 70–80% of commits that don’t include geotagged locations. See <a href="https://zerosixzero.carto.com/viz/d309c729-3a8f-435e-ad1f-b2f4b732ed3d/public_map"><strong>here</strong></a> for an alternate version of this map with commit counts. <strong>In other news, we’re still waiting on our first commits from Africa and Antarctica to have contributions from all seven continents</strong>!</blockquote><h3>15-months of Sensu Enterprise, and Sensu Core version 1.0</h3><p>As told in a <a href="https://sensuapp.org/blog/2016/05/03/from-open-source-to-open-core.html">recent blog post</a>, efforts to improve the open-source Sensu project didn’t really ramp up until I left Sonian in February 2013 to join <a href="http://www.heavywater.io/">Heavy Water</a> and focus on solving monitoring problems on a more regular basis. Two years later, these efforts eventually resulted in Sensu’s shift to an open-core model and the launch of <a href="https://sensuapp.org/enterprise">Sensu Enterprise</a> (in April 2015).</p><p>Although Sensu Enterprise is only 15-months old, it is already fulfilling its purpose as a source of revenue to support future Sensu development. Perhaps more importantly, it has also given our team more opportunities than ever before to learn about how different organizations are using Sensu, and how to support them. This data has not only helped us continue to improve the Sensu Core and Sensu Enterprise software and documentation — it is also enabling us to extend new added-value services to Sensu Core users (more on this below).</p><blockquote><em>You may be wondering — “how is Sensu five years old, and yet it still hasn’t reached version ‘1.0’”?!</em></blockquote><p>We’ve been getting a lot of questions recently about why the Sensu Core project has avoided a “version 1.0” release for so long. It’s definitely not a result of being unfit for production, as Sensu has been battle tested for several years in production environments numbering into the tens of thousands of servers (e.g. at <a href="http://engineeringblog.yelp.com/2015/11/introducing-paasta-an-open-platform-as-a-service.html">Yelp</a> with <a href="https://www.docker.com/">Docker</a> containers, at <a href="https://www.simple.com/engineering/scaling-sensu-by-doing-less">Simple</a> on <a href="https://aws.amazon.com/">AWS</a>, and at <a href="https://www.cloudfoundry.org/ge-leverages-pivotal-cloud-foundry-to-build-predix/">General Electric</a> on <a href="https://www.cloudfoundry.org/">CloudFoundry</a> are just a few of many, many examples). Rather, I’ve always felt that a “1.0” version number should be reserved for when Sensu’s building blocks — the <a href="http://blog.lusis.org/blog/2011/07/21/monitoring-sucks-watch-your-language/">primitives</a> used to solve monitoring problems — would mature to the point where future changes will be minimal, and long-term backwards compatibility can be ensured. I’m very happy to be able to announce at this time that the impending <a href="https://github.com/sensu/sensu/milestones">version 0.26 release</a> of Sensu Core is intended to provide a basis for a “version 1.0” release candidate, and that we are planning to release Sensu Core version 1.0 before the end of Summer. Stay tuned for more information.</p><h3>Let’s celebrate together</h3><p>To celebrate this milestone we are very happy to announce a new service offering for Sensu Core users, and a special promotion for new Sensu Enterprise customers.</p><h4>Enterprise Support for Sensu Core</h4><p>Enterprise Support for Sensu Core provides organizations who are composing monitoring solutions with Sensu Core to take advantage of the same <a href="https://sensuapp.org/support">Enterprise Support SLA</a> and <a href="https://sensuapp.org/training">FREE annual training</a> that are offered to our Sensu Enterprise users, without paying for <a href="https://sensuapp.org/enterprise#the-enterprise-advantage">added-value features</a> which may not be needed within their organizations at this time.</p><p>Enterprise Support for Sensu Core will be available in five (5) pricing tiers, with the same monthly and annual subscriptions as Sensu Enterprise (i.e. get two months FREE when paying annually):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bgm7F7ho0YswKUR4zd7eQg.png" /></figure><p>Enterprise Support for Sensu Core is available for purchase today by <a href="https://sensuapp.org/contact?ref=enterprise-support-for-sensu-core">contacting our sales team</a>, and will become available to purchase through the Sensu website later this month.</p><h4>FREE Professional Services for new Sensu Enterprise Customers</h4><p>Are monitoring improvements on your organizations roadmap? Has your business outgrown your existing monitoring tools? Is your existing monitoring solution having trouble keeping up with improvements to how applications and infrastructure are provisioned or otherwise automated within your organization? Sensu can help!</p><p><strong>Purchase a Sensu Enterprise annual license by July 29th and get up to 200-hours of professional services for FREE (minimum 1000-server license).</strong> Please <a href="https://sensuapp.org/contact?ref=professional-services">contact our sales team</a> today to learn more about this limited-time opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3F5-lV6VDy1eo5nnins86w.png" /></figure><h3>Thank you</h3><p>In closing, I want to personally thank everyone who has contributed to Sensu’s growth over the years — your questions in IRC channels and mailing lists, your GitHub issues and pull requests, and your dollars spent on Sensu Enterprise (and now Enterprise Support for Sensu Core) are all greatly appreciated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94789997a56b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-sensu-blog/five-years-of-sensu-94789997a56b">Five Years of Sensu</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>