~/talk

Detecting the Dip: Building Observability Around...

links:none on file
slides:none on file

Built an anomaly-alert system on Prometheus metrics that predicts per-client traffic using a median of three days (due to three‑day retention) plus a trend correction, and computes adaptive lower bands from a smoothed per-client standard deviation with a fixed 40% margin fallback and historical anchors (1 and 3 days ago minus 2σ). Alerts use a dual gate (prediction + lower band), tiered burn‑rate thresholds and windows; result: caught a medium‑traffic regression ~90 minutes after deploy and a low‑volume bank degradation in 30 minutes.

AI-written summary · about

  1. 0:00Introduction and background
  2. 1:08Pain points with integrations
  3. 3:57Defining observability goals
  4. 5:21Data collection initiative
  5. 7:50Anomaly detection basics
  6. 10:21Predicting traffic patterns
  7. 12:26Calculating alert bands
  8. 16:21Alert thresholds and burn rates
  9. 19:13Dual-gate alert logic
  10. 21:19Real-world incident detection
  11. 22:41Key takeaways and Q&A
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.