Practical implementation guides

OpenTelemetry Implementation Guides

Choose a starting point, implement one useful capability at a time, and validate the signal before adding more complexity.

Implementation guide

APM Implementation Guide

Instrument a service from its first exported traces to actionable service health, release comparison, log correlation, and operational coverage.

8 min read

Implementation guide

Make Lambda functions visible with AWS-native metrics, the OpenTelemetry layer, structured logs, and application traces.

9 min read

Implementation guide

Use Grafana Faro to capture browser errors, views, Web Vitals, and selected frontend journeys without collecting customer data by accident.

6 min read

Implementation guide

Connect request-level database spans with PostgreSQL health, pool behaviour, query evidence, and operational response.

10 min read

Implementation guide

Collect Kubernetes node, cluster, workload, log, and inventory signals in an order that keeps ownership and validation clear.

7 min read

Implementation guide

Trace model calls, retrieval, tools, cost signals, and policy-safe prompt visibility without losing the customer request that explains them.

10 min read

Implementation guide

Build a dependable log path with deliberate collection ownership, parsing, infrastructure context, and trace correlation.

10 min read

Implementation guide

Make the Collector observable with self-metrics that expose queue pressure, export failures, rejected telemetry, and platform-owned response.

6 min read

Implementation guide

Equip a read-only investigation agent with Tsuga access, code context, incident facts, guardrails, and a repeatable validation process.

9 min read

Implementation guide

Operate a Linux VM Collector that captures host evidence, Collector health, local logs, and OTLP from local applications.

8 min read