Operations | Monitoring | ITSM | DevOps | Cloud

Sensu

Puppet Sponsor Session at Sensu Summit 2018

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.

Project 3M: Meaningful Monitoring and Messaging at Sensu Summit 2018

In this talk from Sensu Summit 2018, Christopher J. Caillouet, Senior Dev|Ops Production Engineer at Industrial Light & Magic, looks behind the curtain and sees how the intelligence and uptime they gain by leveraging Sensu in the ILM monitoring infrastructure enables reliability and stable delivery within a large scale and geographically distributed set of datacenters.

Pull, don't push: Architectures for monitoring & config in a microservices era at Sensu Summit 2018

In this Sensu Summit 2018 talk, Chef's Julian Dunn & Fletcher Nichol give you a primer about promise theory and the autonomous actor model that underlies the design of products like Sensu and Habitat, why it leads to not only higher overall system reliability but human comprehension for easier operations.

Migrating to Sensu, as told by a Nagios refugee

One of our favorite stories at Sensu is hearing how our customers are using, repurposing, and even replacing their Nagios setup. The Sensu monitoring event pipeline lets you run your existing Nagios plugins while also preparing you for what’s next; while Nagios has been tried and true for many, Sensu empowers businesses to modernize their infrastructure with a comprehensive, future-proof monitoring solution.

Migrating to 2.0: the good, the bad & the ugly

The Sensu 2.0 release is dropping in October, and we’re already excited! As the version numbering implies, Sensu 2.0 includes significant changes from Sensu 1.x. Not only has the software been entirely re-engineered in Go — easing deployment significantly — the exposed APIs and internal data structures have changed to accommodate new features.