The Future of Sensu

Transcript

1. The Future of Sensu Sean Porter - CTO for Sensu

   Inc.

2. The Present • Mature monitoring primitives ◦ Focus on composability

   and extensibility • Built for any scale ◦ Leveraging well tested and common technologies ◦ Architected for dynamic environments

3. The Present • Monitors a broad portion of the technology

   spectrum ◦ Bare metal to containers • Designed for DevOps workflows ◦ Automation (e.g. Puppet) ◦ Version control

4. Our mission: Obviate the need to (re)build custom monitoring solutions.

5. None

6. “You can only know where you’re going if you know

   where you’ve been.”

7. Sources of Friction • RabbitMQ and Erlang • HA Redis

   • Reliance on configuration management • Lack of multi-tenancy
8. None
9. None

10. We are building...

11. Sensu 2.0 • No external transport • No external data

    store • Does not rely on configuration management • Multi-tenancy and RBAC from the ground up
12. None

13. Sensu 2.0 • Written in Go • Implements the Sensu

    PubSub model (push + pull) • ALL configuration is done via the API • Check runtime asset management

14. Sensu 2.0 • Entities (instead of “clients”) ◦ Can represent

    anything (e.g. agent, router, function, etc.) • RBAC Organizations and Environments
15. None

16. DEMO

17. Thank You.