Observability from 0 to 100
summary
Shows a concrete Elastic-based rollout: install agents as a daemonset managed by Elastic Fleet, enable ECS JSON logs to avoid costly Logstash processing, add the Java APM agent to instrument services without code changes, and create one spike service as a blueprint before cluster-wide rollout. Tune alert thresholds, sample traces (always capture failures), apply retention tiers or rollups to control cost, and expect OpenTelemetry to be useful but not yet a full replacement.
AI-written summary · about
chapters (12)
- 0:00What is observability?
- 1:44Metrics logs events traces
- 3:49Structured logging benefits
- 8:41Collecting telemetry data
- 10:26Tuning alerts thresholds
- 11:29Start small and budget
- 13:57Elastic Fleet setup
- 18:09Collecting traces with APM
- 20:35Fine-tuning observability data
- 24:49OpenTelemetry standards
- 28:21Key takeaways and goals
- 29:27Q&A session
related talks
10mEffective Observability: Best Practices with Elastic
46mObservability in the real world: Improve systems w/iterative approach
17mHow Observability-First Development Lets You Ship Agents in Weeks...
52mGrowing to full-suite observability with Elasticsearch & the ELK Stack (PRT267)
34mMonitor Kubernetes cluster with Elastic
29mObservability; a gentle introduction
29mLicense to Observe - Why observability solutions need agents
56mFull-stack observability and application monitoring with