Observability best practices for hybrid environments
summary
Outlines a concrete path: adopt OpenTelemetry collector for uniform receipts/processors/exporters, enforce minimal tags/attributes and context propagation to cut MTTR, and apply data tiering (A/B/C) so metrics and traces stay real time while logs age to S3. Demonstrates the Splunk Observability Cloud with an APM service map, always-on code profiling, and a new federated search for S3, claims a 14-day free trial and POC options, and shows these pieces working together to surface root causes across hybrid on‑prem and AWS environments.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:04What hybrid environments mean
- 9:22Observability vs monitoring
- 16:32OpenTelemetry data collection
- 22:33Best practices for hybrid implementation
- 34:04Data tiering and prioritization
- 39:27Splunk Observability Cloud demo
- 44:09Q&A and resources
related talks
56mFull-stack observability and application monitoring with
42mUnified observability, AIOps, and incident response for AWS
01h 01mBetter reliability and uptime with analytics and observability
37mBuilding Modern Observability Architecture With OpenSearch, OS Ingest...
24mObservability with AWS
20mDesigning the Right Observability Stack in AWS Cloud
33mWhat Developers Should Know About Observability
10mEffective Observability: Best Practices with Elastic