Sensu Inc. is the creator and maintainer of Sensu, the open source monitoring event pipeline. Founded in 2017, Sensu empowers businesses to automate their monitoring workflow and gain deep visibility into their infrastructure, applications, and operations. Backed by one of the largest open source communities in monitoring, companies like Netflix, General Electric, and the Associated Press rely on Sensu to help them deliver value to their customers faster, at larger scale. Sensu maintains the free and open source Sensu Core framework as well as the commercially supported Sensu Enterprise, which offers enhanced features to simplify operations and governance, with multi-cloud support for monitoring at scale.
Headquartered in Portland, Oregon, Sensu currently operates as a fully distributed team, with employees located throughout the United States and Canada. For more information, follow @sensu on Twitter or visit https://sensu.io.
In my previous post, I talked about the real costs of alert fatigue — the toll it can take on your engineers as well as your business — and some suggestions for rethinking alerting. In part 2 of this series, I’ll share some best practices for fine-tuning Sensu to help reduce alert fatigue.
Alert fatigue occurs when one is exposed to a large number of frequent alarms (alerts) and consequently becomes desensitized to them.
At Monitorama 2018, I shared some of the cool process and knowledge I’ve learned from developing a product for people other than myself to consume.
NGINX can be used as a proxy to provide authenticated access to specific endpoints for any RESTful service API — including the Sensu API. Below I provide an NGINX configuration to grant external service provides narrow access to only create check results in the Sensu 1.4 API external service providers.
At Sensu, we define monitoring as "the action of observing and checking the behavior and outputs of a system and its components over time." Essentially, you want to be made aware of a problem before your users are.
Increasingly complex systems make availability and performance monitoring more difficult than ever before, especially for container-based, multi-cloud, and hybrid-cloud infrastructures.
Sensu enterprise customer Christopher Sabo shares the details of his Sensu implementation with Puppet, Docker and more at Netsmart Technologies.
In this Sensu Summit 2018 lightning talk, Paul Czarkowski of Pivotal talks about the death of DevOps and servers (plus a brief history of terms and their evolution).
In this talk from Doximity's Ben Abrams (from Sensu Summit 2018), you'll learn: Why alert fatigue is dangerous…
In this talk from Sensu Summit 2018, Garrett Honeycutt showcases the Puppet module: its current state; support for Sensu 2.0; highlight community contributions and how you can contribute. You’ll see the Vagrant setup and how even if you don’t use Puppet, you can easily get Sensu up and running on a bunch of different platforms.
For the last two years, David Schroeder, Software Engineer at Viasat, Inc. has supported a single Sensu cluster shared by multiple teams, each with their own requirements, thresholds, and contacts. How does it all work, how can these different uses coexist?