Sensu Summit - The Future of Sensu

The Sensu 2017 Summit keynote.

Transcript

1. The Future Of Sensu Sean Porter - CTO @PorterTech
2. Welcome
3. 27,368 commits 1349 contributors > 500k monthly downloads
4. Why Do We Care About Monitoring? • We deliver value with software • Software availability is critical - downtime is expensive! • We must have visibility into our systems
5. Monitoring is a core competency.
6. The Origin Story
7. The Origin Story I joined Sonian in 2010 as an “Automation Engineer” • Early adopters • High rate of change ◦ Growing team ◦ Evolving software stack
8. I experienced a HUGE paradigm shift in infrastructure delivery.
10. We designed our software for the cloud.
11. We designed our software for the cloud. We did NOT design our monitoring tools...
12. The Tools We Knew
15. Too much monitoring.
16. Limitations of the technology.
17. Use vs build vs buy?
19. The Origin Story I started a side project (July 2011) • An agent based monitoring system with auto-discovery ◦ Leverage existing and familiar technologies, protocols, etc. ◦ Easy to drive with configuration management ◦ Easy to scale ◦ APIs
20. The Origin Story • Named it Sensu • Sonian sponsored development! ◦ Deployed to production after 2 months of development • Sensu evolved into a “monitoring framework” ◦ Composable event processing pipeline
21. Sensu was designed for the cloud*
22. Sensu was created in response to a paradigm shift in infrastructure delivery.
23. Open Source
24. November 1st, 2011.
26. Sensu has grown more powerful.
27. Heavy Water I joined Heavy Water in 2013 as a partner • We launched sensuapp.org • We helped all kinds of organizations use Sensu ◦ Gained insight into monitoring challenges • We created Sensu Enterprise! (April 2015)
28. Sensu Inc.
29. Sensu’s mission: Obviate the need to (re)build custom monitoring solutions.
30. Together we are creating a better Sensu.
31. We Shipped Sensu 1.0!
32. Sensu 1.0 • Mature monitoring primitives ◦ A focus on composability and extensibility • Built for any scale ◦ Leveraging well tested and common technologies ◦ Architected for dynamic environments
33. Sensu 1.0 • Monitors a broad portion of the technology spectrum ◦ Bare metal to containers • Designed for DevOps workflows ◦ Automation (e.g. Puppet) ◦ Version control
34. Sensu 1.x Roadmap • Scheduled maintenance • Check hooks! • Official Docker images
35. Next Steps?
36. Make it easier.
37. Sources Of Friction • RabbitMQ and Erlang • HA Redis • Reliance on configuration management • Limited multi-tenancy capabilities • Footprint
38. Prepare for the future.
39. We are experiencing another paradigm shift in infrastructure delivery.
40. The container paradigm.
41. Sensu 2.0
42. Sensu 2.0 • Same core principles • Same primitives • Will support everything Sensu does now
43. Sensu 2.0 is easier.
46. Sensu 2.0 • Better APIs • Entities ◦ Host, VM, container, function, etc. • Metrics are first class!!!
47. Sensu 2.0 is designed for containers the future.
48. Greg Poirier - VP of Engineering Sensu 2.0 Technical Deep Dive @ 4:40
50. You can be an alpha tester.
51. Thank You Sean Porter - CTO @PorterTech