OpenTelemetry Demo

OpenTelemetry Demo is a self-hosted reference application that simulates a realistic multi-service e-commerce site to generate traces, metrics, and logs for…

  • Development
  • Tools & Utilities
OpenTelemetry Demo is a self-hosted reference application that simulates a realistic multi-service e-commerce site to generate traces, metrics, and logs for testing and benchmarking observability tooling. Run it on a homelab or in CI to validate OpenTelemetry collectors, exporters, and backends such as Prometheus, Jaeger, and Grafana without risking real production traffic.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

64/100 Good

Maintained
100last commit 16 days ago
Popular
713,440 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
201 serious finding, 3 minor, CI, tests, OpenSSF Scorecard 7.9/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
3,440
Open issues
73
Last commit
2026-11-05
Latest release
3.1.0
License
Apache-2.0
Activity
steady

Checked 15 days ago - source: GitHub (open-telemetry/opentelemetry-demo)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set service name and OTLP endpoint Before starting the app, open the YAML config file and replace SERVICE_NAME and OTLP_ENDPOINT (the network address of your OpenTelemetry collector). If you don't, your app won't identify itself or send tracing data to the right place. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I push OpenTelemetry metrics to a self-hosted Grafana container?

A community thread asks how to push OpenTelemetry metrics from a custom app into a self-hosted Grafana container. It frames the change as replacing an older pull-based metrics setup with a more standardized OTel approach.

Can a self-hosted backend accept spans, metrics, and logs?

A community question asks whether any self-hosted OpenTelemetry backend can accept spans, metrics, and logs. It notes that the asker previously relied on Azure Application Insights for all three signal types.

What should I expect when moving from a commercial APM vendor to an open-source OpenTelemetry stack?

A Reddit thread asks people who moved from vendors such as Datadog, New Relic, or Splunk to Grafana Cloud or open-source OpenTelemetry stacks to share their experience. It also asks how the new stack handles scale.

What does the demo's self-observability dashboard show?

It uses OpenTelemetry SDK internal metrics, based on the experimental otel.sdk.* conventions, to describe SDK behavior. Examples include dropped telemetry, export duration, and processor queue fill.

Where should I ask questions about the demo?

The GitHub Discussions forum is where users can explore the demo, discuss code, ask questions, and collaborate with the developer community.

Answers sourced from community.grafana.com, github.com, opentelemetry.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads