Please Standby Well be starting shortly 1 Monitoring as Code With - - PowerPoint PPT Presentation

please standby we ll be starting shortly
SMART_READER_LITE
LIVE PREVIEW

Please Standby Well be starting shortly 1 Monitoring as Code With - - PowerPoint PPT Presentation

Please Standby Well be starting shortly 1 Monitoring as Code With Sensu + Ansible Jef Spaleta (Sensu) Tadej Borovak (Xlab Steampunk) XLAB Steampunk Helping ISVs build high-quality Ansible Collections. Design & Maintenance &


slide-1
SLIDE 1

Please Standby We’ll be starting shortly

1

slide-2
SLIDE 2

Monitoring as Code With Sensu + Ansible

Jef Spaleta (Sensu) Tadej Borovšak (Xlab Steampunk)

slide-3
SLIDE 3

Helping ISVs build high-quality Ansible Collections.

XLAB Steampunk

galaxy.ansible.com/steampunk galaxy.ansible.com/sensu/sensu_go

Design & Development Maintenance & Support Certification

slide-4
SLIDE 4

We take Steampunk very seriously!

slide-5
SLIDE 5
  • What is Sensu?
  • Monitoring as Code

vs Infrastructure as Code

  • Introduction to

Sensu Go Ansible Collection

  • Automating remediation of

Sensu events using Ansible Tower

Overview

5

slide-6
SLIDE 6
  • Turn-key Observability Pipeline for any cloud
  • Unified infrastructure and application monitoring-as-code
  • Automation for DevOps and SRE teams
  • Reuse existing tools (Nagios, Telegraf, StatsD, Prometheus)
  • Complete visibility, from bare metal to Kubernetes

What is Sensu?

6

slide-7
SLIDE 7
  • Eliminate data silos by integrating with existing systems of

record, and data platforms like ElasticSearch, Splunk!

  • Fill gaps in observability tooling between metrics, logging, and

tracing

  • Consolidate monitoring tools with support for existing plugins

& exporters (Nagios, StatsD, Telegraf, Prometheus, Sensu)

  • Automate diagnosis & self-healing with built-in auto-

remediation or integrations with Ansible Tower, RunDeck, and SaltStack

Sensu Use Cases

7

slide-8
SLIDE 8

What is Sensu?

  • Agent-based monitoring & observability
  • Flexible subscription model for service-based monitoring
  • RBAC, Rest API with web and cli client interfaces
  • Powerful event pipeline: alerting, data routing & remediation

8

slide-9
SLIDE 9

What is Sensu?

But wait there’s more!!!!!

  • Declarative configuration files for all pipeline elements
  • Extensible with shareable assets (https:/

/bonsai.sensu.io)

  • Process both metrics and service checks

9

slide-10
SLIDE 10

Monitoring + Automation

Why Monitoring? Provides the necessary, actionable information about failures, defects or problems in the system.

10

Why Automation? Makes complexity manageable. Automation reduces the need to perform repetitive or tedious manual tasks, freeing up human resources for innovation.

slide-11
SLIDE 11

Monitoring + Automation

Sensu: Monitoring as Code Declare all your monitoring workloads as simple to understand resource collections.

11

Ansible: Infrastructure as Code Automate provisioning of infrastructure and services (like Sensu) using declarative idempotent playbook resources.

slide-12
SLIDE 12

Sensu Go Ansible Collection

12

Collections are great advancement for Ansible community

  • Packages modules and roles together!
  • Available in Ansible Galaxy (or private sources)
  • Modules no longer tied to to Ansible releases
  • Sensu Go Collection can be updated/released in

conjunction with upstream Sensu Go releases

slide-13
SLIDE 13

Sensu Go Ansible Collections Demo

13

slide-14
SLIDE 14

Sensu: Monitoring as Code

Key Concepts:

Entity: agents + proxies Checks: scheduled monitoring workloads run by agents Observability Pipelines: filter + transform + process Events: the base data structure Sensu Go pipeline processes Subscriptions: loosely couples checks to entities Assets: sharable binaries to support monitoring workloads, Sensu installs at runtime without the need to pre-provision hosts.

14

slide-15
SLIDE 15

Sensu Demo Building a Monitoring Workflow

15

slide-16
SLIDE 16

16

slide-17
SLIDE 17

Self-healing Infrastructure

17

Close the loop between monitoring and automation for better alerts. Use operator knowledge encoded in Ansible Tower automation to resolve Sensu events. Only escalate alerts to humans for situation existing playbooks can’t resolve!

17

slide-18
SLIDE 18
  • Sensu Ansible Tower integration

○ Uses Ansible Tower Jobs Template API ○ Granular flow control when Ansible Tower jobs are triggered

  • Benefits

○ Reduce alert fatigue by leveraging Ansible playbooks as remediation tools ○ Allows for further escalation if automation fails to resolve Sensu event

18

Self-healing infrastructure with Sensu + Ansible

18

slide-19
SLIDE 19

Self-healing Infrastructure as code

19

slide-20
SLIDE 20

20

slide-21
SLIDE 21

Sensu Monitoring as Code: Recap

21 21

  • Declarative resources, manageable via API

using the Ansible Sensu Go collection or using sensuctl

  • Subscriptions, loosely coupling service monitoring

workloads with operational infrastructure

  • Assets let you update monitoring workloads without

re-provisioning infrastructure

  • Sensu + Ansible Tower = Self-healing infrastructure
slide-22
SLIDE 22

Next Steps with Sensu

  • Watch our on-demand webinar on how to use the

Sensu Ansible Tower integration

https:/ /sensu.io/resources/webinar/self-healing-workflows-with-the-sensu-ansible-tower-integration

  • Join the Sensu Community

http:/ /discourse.sensu.io/signup

  • Contact us for a 1:1 demo

https:/ /sensu.io/contact

22 22

slide-23
SLIDE 23

Curious to know more about testing collections?

steampunk.si/webinars-training/intro-testing-ansible-collections Visit us: steampunk.si Reach out to us: steampunk@xlab.si

Watch our free webinar

Testing Ansible Collections

available on demand

slide-24
SLIDE 24

End

24