Unified observability, AIOps, and incident response for AWS
summary
Claims that OpenTelemetry is the recommended ingestion layer and Splunk APM captures every transaction, no sampling. Demo shows APM finding root cause in six minutes for a heavy service doing ~200 queries/sec where one host’s P90 climbs to ~30s vs normal ~2s. Splunk layers logs, traces, metrics and topology into a unified Incident Intelligence workflow (public preview Dec 12) that groups alerts, maps responders by schedule, and drives on-call notifications and automated actions.
AI-written summary · about
chapters (6)
- 0:00Introduction to observability
- 1:23Challenges in modern IT
- 9:05Defining observability
- 17:49OpenTelemetry overview
- 22:11Incident intelligence
- 32:37Product demo and conclusion
related talks
46mObservability best practices for hybrid environments
41mCustomer Centric Observability at Scale Leveraging AIOps & OpenTelemetry
56mFull-stack observability and application monitoring with
01h 01mBetter reliability and uptime with analytics and observability
49mBuilding digital resilience with unified security and observability
37mBuilding Modern Observability Architecture With OpenSearch, OS Ingest...
27mOpenAPM – Application Performance Management tailored to your needs
24mObservability with AWS