Why OpenSearch?
summary
Community build claims a full rewrite of Lucene to store logs, traces, and metrics in a single index, and reports native ingestion from OpenTelemetry connectors so you can feed Databricks and Spark logs and host metrics directly. Benchmarks promised: noticeably cheaper and faster analysis than typical observability stacks within months, with a simplified query experience for telemetry. Practical notes: teams report trouble with Loki adoption and currently focus on logs + JVM/Kubernetes metrics while traces remain exploratory.
AI-written summary · about
related talks
06mSponsored Keynote: OpenSearch - See Everything: Open Observability for Agentic AI
20mSeeing Is Believing: OpenTelemetry and OpenSearch in Next-Gen Observability
21mKubernetes Under the Magnifying Glass: Observability With OpenSearch
25mUnifying Observability: Weaving Prometheus, Jaeger, and Open Source Together to Win
22mFrom Telemetry to Insight: Building AI-Powered Observability Pipelines with OpenSearch
42mObserve Smarter, Not Harder: Scaling AI-Powered Observability With O...
20mMeasuring Data with OpenSearch to Better Serve the Community
29mOpenTelemetry With OpenSearch: Use-Cases, Status and Roadmap