A telemetry data generator, by XplurData

You built the dashboards. You wrote the alerts.
But there's no real traffic yet to know if any of it works.

OTel Studio generates that traffic for you — realistic, correlated traces, logs, and metrics across 25 service topologies, sent to any OTel-compatible backend in 60 seconds. No code, no app to deploy.

Quick Start → View on GitHub
25 Scenarios· 12 Stack Presets· 3 Correlated Signals· MIT Licensed 
docker run -d --name otel-studio -p 3002:3002 \
  -e OTEL_ENDPOINT="http://your-collector:4317" \
  -e OTEL_PROTOCOL="grpc" \
  -e ADMIN_PASS="your-password" \
  otel-studio:latest

How it works

Four steps from zero to realistic, correlated telemetry.

1

Pick a scenario

Choose from 25 realistic service topologies — or run several at once.

2

OTel Studio generates correlated data

Traces, logs, and metrics with matching trace IDs, real parent-child span chains.

3

Sent via standard OTLP

gRPC or HTTP, to one endpoint or several simultaneously.

4

Lands in your backend

Grafana, Datadog, SigNoz, Honeycomb, or any OTel-compatible tool — no code required.

The gap between too simple and too heavy

Most observability teams can't test their pipelines realistically because they don't have good data generators.

ToolLimitation
telemetrygenCLI-only, random data, no service topology, no UI
hotrod / astronomy-shopFull demo apps — heavy to deploy, not configurable
k6 / GatlingLoad-testing tools, not observability-focused — no trace/log/metric correlation
Hand-written scriptsEvery team reinvents the same wheel

Everything you need to test a real pipeline

Not random noise — actual request chains with parent-child spans, correlated logs, matching metrics.

🗂️

25 Scenarios

Web App, Infrastructure, APM, Cloud Native, and Chaos/Stress topologies — real parent-child request chains, not random data.

🔗

Correlated Signals

Logs share trace IDs with the spans that produced them. Search a trace ID, see the matching logs and metrics.

⚡

Chaos Scenarios

Dedicated error-storm, cardinality-burst, and latency-spike modes for testing alerting and dashboards.

🔀

Multi-Endpoint Fanout

Send to two or more OTel backends simultaneously, with independent TLS/mTLS per endpoint.

🌍

Geo / IP Simulation

Tag generated telemetry with realistic regional IP ranges, or safe RFC 5737 test ranges.

🪪

Synthetic PII

Opt-in, per-scenario synthetic user data for testing redaction and DLP pipelines — never real people's data.

📡

Real System Data

Optionally tail real log files and Docker container logs/metrics alongside simulated traffic.

🎛️

One-Click Stack Presets

Grafana Alloy, OTel Collector, Elastic APM, Honeycomb, Jaeger, SigNoz, OpenObserve, Datadog, New Relic, Dynatrace, Lightstep.

Real depth, not just a demo toggle

Every scenario has an Advanced panel — geo/IP simulation, synthetic PII, custom attributes, span duration overrides, weighted status codes.

OTel Studio Advanced Settings panel showing Geo/IP simulation, Synthetic PII, and custom attribute controls

Who it's for

SREs

Setting up a new o11y stack who need realistic data before they have real production traffic.

Platform Teams

Demoing a new backend to stakeholders without waiting on a live integration.

Developers

Writing alert rules or dashboards who need controllable error/latency scenarios to test against.

Open Source Projects

Tools like SigNoz, OpenObserve, and Coroot needing a test data generator for their own CI/testing.

Ready to try it?

Docker-deployable in under a minute. No account, no cloud dependency.

Read the Quick Start →