Measuring Data with OpenSearch to Better Serve the Community
summary
OpenSearch and OpenSearch Dashboards power a small analytics stack that scrapes forums, GitHub and the Twitter search API to produce actionable metrics: project stats (1.4M downloads, 70+ repos, 3,300+ forum users), a heatmap that surfaces configuring and troubleshooting as top pain points, a Twitter scrape that finds 239 tweets vs 14 from traditional mention tools and reveals 30% Japanese volume, and a runnable connector set called Community Pulse delivered as Docker-compose so teams can reproduce and act on gaps.
AI-written summary · about
chapters (12)
- 0:00OpenSearch Community Data
- 1:53Community data needs observability
- 3:17Building open source incrementally
- 4:44Heat maps for Discourse conversations
- 7:35Drilling into discussions
- 8:59Beyond Twitter monitoring
- 11:06Multilingual community insights
- 12:55OpenSearch capabilities overview
- 15:22Observability for community impact
- 16:46Open source collaboration power
- 18:10OpenSearch Dashboards playground
- 18:58Community Pulse Tool future
related talks
06mSponsored Keynote: OpenSearch - See Everything: Open Observability for Agentic AI
20mExtending OpenSearch Dashboards: Building a Unified Obser...
28mThe top five things to know about OpenSearch
06mWhy OpenSearch?
38mOpen-source Dashboarding Tools. Which One Suits You?
42mObserve Smarter, Not Harder: Scaling AI-Powered Observability With O...
25mUnifying Observability: Weaving Prometheus, Jaeger, and Open Source Together to Win
15mFrom Top N Lists to Visual Analytics: Query Insights Dashboard in OpenSearch
