May 10, 2026

Why Telemetry?

Telemetry is older than computing, older than radio. A short history that explains why software emits the data it does, and why the OpenTelemetry standard finally got the design right.

Why Telemetry?

Telemetry means "measuring at a distance" and is older than computing.

A short history

History content lives in another working draft (Mont Blanc weather observations, early Russian rocketry, telephone monitoring, WWII, NASA, the move from radio telemetry into networked-software telemetry, the rise of distributed systems, the proprietary-vendor era, and finally OpenTelemetry). Paste here when ready.

Telemetry in software

When software inherited the word, it inherited the constraint with it. Your service runs in a datacenter you don't physically touch. Your mobile app runs on a phone in a stranger's pocket. Something goes wrong; you need to know what, and where, and why — without being able to attach a debugger.

For decades the answer was an awful proliferation of vendor-specific agents, log shippers, and metric collectors. Every observability vendor had their own SDK, their own tagging conventions, their own performance tradeoffs. Switching vendors meant re-instrumenting every service and every app.

OpenTelemetry is the long-overdue resolution. The world finally has one vendor-neutral standard for emitting traces, metrics, and logs.

Why OpenTelemetry got the design right

A few things make OTel the standard worth adopting now:

  • Pluggable, vendor-neutral protocol. OTLP (the OpenTelemetry Protocol) is the wire format every backend speaks. You instrument once, point your collector at whoever you want.
  • Strong semantic conventions. OTel publishes a registry of standard attribute keys — http.request.method, db.system.name, service.name. When everyone uses the same keys, dashboards and alert rules port across vendors.
  • It's a CNCF project. The OpenTelemetry project is the second-most active project at the Cloud Native Computing Foundation, after Kubernetes. The bus factor is high.

For Flutter and Dart, the historical gap was that Dart was the last of the seventeen first-class OpenTelemetry languages to get an implementation. Until now, "we use OTel" implicitly meant "for everything except our Flutter app." That gap is what dartastic_opentelemetry closes.

Where Dartastic fits

Dartastic is the Dart and Flutter implementation of OpenTelemetry. It's spec-compliant, it ships traces, metrics, and logs, and it works across every Dart platform — server, mobile, web, desktop, Wasm.

But more importantly: it lets your Dart and Flutter code participate in the same observability story as the rest of your stack. One trace ID can flow from a Flutter UI tap, through your Dart backend, into a Postgres call, into a third-party API — and you can see the whole thing in one place.

That's the promise telemetry has been making for two centuries. Now Dart and Flutter get to keep it.

Read more: Why OpenTelemetry? · Pricing

All posts telemetryhistoryobservability