From Logs To Signals: Rethinking System Monitoring With OpenSearch
summary
Argues that structured JSON logs become first-class signals indexed into OpenSearch so sliding‑window aggregation queries continuously evaluate system state rather than relying on post‑hoc log searches Metrics still detect but logs produce explicit outcomes like REGION_OUTAGE by running per‑dependency, per‑error aggregations The demo uses a Go checkout service with 50% injected failures and an OpenSearch monitor firing at a 20% error threshold every minute to return context‑rich alerts.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 1:03Current monitoring workflow
- 3:11Logs as signals
- 5:42Structured logs requirements
- 7:28Demo setup with OpenSearch
- 11:02Dependency failure alerts config
- 13:29Context-rich alerts
- 14:34Reducing investigation delay
- 15:38Limitations and best fit
- 17:03Key takeaways
- 17:45Q&A
related talks
22mFrom Telemetry to Insight: Building AI-Powered Observability Pipelines with OpenSearch
42mObserve Smarter, Not Harder: Scaling AI-Powered Observability With O...
01h 15mMonitoring: Turning Noise into Signal
20mSeeing Is Believing: OpenTelemetry and OpenSearch in Next-Gen Observability
37mBuilding Modern Observability Architecture With OpenSearch, OS Ingest...
21mKubernetes Under the Magnifying Glass: Observability With OpenSearch
34mHow to Do Microservice Observability with OpenSearch
12mOpen-source observability is the way forward, and here’s why