~/talk

Chaos Experiments under the lens of AIOps

slides:none on file

MiniKube ecommerce demo with ~10–11 microservices uses Splunk Observability + an AIOps layer, litmuschaos to inject 4,000 ms network latency into the card service for 200s, and locust simulating 30 users (spawn rate 2). Splunk detects and alerts on latency and issues a prediction before the peak, a dashboard counts litmus-triggered pod launches, and a runbook can auto-remediate (rebuild/reset). Hypothesis that AIOps recognizes and responds to chaos experiments is proven by the live demo.

AI-written summary · about

  1. 0:00AIOps and chaos engineering intro
  2. 1:04AIOps vs chaos engineering
  3. 3:09AIOps observe engage act model
  4. 5:13Planning chaos experiments
  5. 6:37Setting chaos hypothesis
  6. 8:00Live demo environment
  7. 10:25Injecting latency with Litmus Chaos
  8. 13:18AIOps response to chaos
  9. 16:30Detecting chaos via observability
  10. 17:13Summary
~/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.