Supercharge your incident response with Trek10 and Datadog
summary
Claims a shrink in IR time by automating triage, remediation and recovery using Datadog and Trek10 patterns, with concrete tools: Jupyter notebooks as runbooks, EventBridge→Datadog webhook for unified signals, and a Slack approval flow that turns alerts into saved actions and incident notebooks. Demo shows a CloudTrail CreateAccount event routed to Datadog, a Slack yes/no gating decision, and an automated notebook launch; advice is to document, test off‑prod and add guardrails.
AI-written summary · about
chapters (15)
- 0:00Introduction and presenters
- 1:03Incident response is preparation
- 3:54Observability and automation basics
- 7:43OODA loops in incident response
- 10:10Automation principles and guardrails
- 14:27Security as part of incident response
- 16:56Shared observability with Datadog
- 20:29First incident response demo
- 25:14ChatOps and human interaction
- 28:13Detection and response flow
- 31:42Second incident response demo
- 38:05Considerations and testing
- 39:50Security is a continuous journey
- 40:12Documentation and testing importance
- 41:37Key takeaways and to-dos
related talks
34mIncidents Happen
33mAutomation Best Practices for SRE and Security
38mDemocratizing Observability
28mPatterns for scalable security detections on AWS
28mThe Agent That Turned On-Call Chaos into a Single Slack Thread
45mJourney to Securing the Cloud: Detecting and Fixing Misconfigurations at Datadog
31mThe Art of Turning Incidents into Opportunities
01h 41mDatadog DASH 2019 Keynote