~/talk

How I Automated Incident Management

TalkinFrenchat XebiCon'17 · on Thursday, 2017-11-30· [devops-and-delivery, observability]
slides:none on file

An automated incident-management pipeline that parses natural-language messages using fuzzy dialogue techniques, stores incidents as documents in Elasticsearch, creates Jira tickets, opens a dedicated chat room, updates a public status page, and posts follow-ups. The prototype is implemented in under 500 lines of Python (built in about 13 hours), recognizes intents (open/update/close/list), deduplicates recent reports, logs timestamps and priorities, and exposes incident data for dashboards and further automation.

AI-written summary · about

  1. 0:00Incident automation intro
  2. 3:30Manual incident problems
  3. 5:14Dialogflow automation
  4. 7:42Live app demo
  5. 12:19Data analysis improvements
  6. 15:27Conclusion future outlook
  7. 16:32Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.