OpenTelemetry

OpenTelemetry traces: why deprecating span events is a terrible idea

OpenTelemetry GenAI semantic conventions, hands-on: auto-instrumentation, agent and tool spans, token usage and cost, and where to send the traces.

Treating a Gaggia espresso machine like a distributed system: instrumenting an ESP32 with OpenTelemetry, streaming shots and whole-house sensors into ClickHouse Cloud, and putting ClickStack (plus an LLM agent) on top to turn every pull into a queryable,

OpenTelemetry as system dependency Setting up OpenTelemetry for your applications and systems depends on where those apps and systems run. Some are very automated, especially Kubernetes, thanks to the OpenTelemetry Operator, or AWS Lambda, with the OpenTe

A complete guide to the OpenTelemetry Collector: agent vs. gateway patterns, YAML configuration, tail sampling, and production best practices.

If you write Java, Python, Node.js, or .NET, you have been able to add OpenTelemetry to an application without editing its code for years: attach an agent at startup and telemetry starts flowing. Go has been the exception. A Go program compiles to a singl

Traces and spans arent just two levels of the same hierarchy Learn how OpenTelemetry models them at the protocol level and when to use each view fordebugging production systems

Monitor your n8n workflows with OpenTelemetry: capture execution traces, metrics, and failures in one place.

Measure whether Claude Code is degrading using OpenTelemetry, with output-per-token metrics, dashboards, and efficiency alerts.

ArcadeDB adds OpenTelemetry tracing, RED latency metrics with OTLP export, structured JSON logging with correlation IDs, and Kubernetes health probes. Every one of them is opt-in and backward compatible.