← Back to guidesGuide

Validate Linux host metrics with OpenTelemetry Collector before dashboards go empty

A practical canary for separating install issues, resource identity drift, exporter queues, and backend freshness before rolling the Collector across the fleet.

Learn how to validate an OpenTelemetry Collector hostmetrics pipeline on Linux with systemd, self-telemetry, Prometheus, and rollout guardrails before trusting dashboards that have not proven anything yet.

Created: July 28, 2026

Published: July 28, 2026

Estimated time35 min

LevelIntermediate

Before you startA Linux canary host with systemd and permission to install or edit OpenTelemetry Collector.

PlatformsLinux / Docker

WhatsApp X LinkedIn

Docker

Run the same canary in a Collector container by mounting the local config and exposing the self-telemetry port.

Dockernetwork path to the OTLP gatewaylocal config.yaml

Start canary

docker run --rm --name otelcol-canary -p 8888:8888 -v "$PWD/config.yaml:/etc/otelcol/config.yaml" otel/opentelemetry-collector-contrib:latest --config=/etc/otelcol/config.yaml

Check internal metrics

curl -s localhost:8888/metrics | grep otelcol_exporter_queue_size

Also available inValidar métricas de hosts Linux con OpenTelemetry Collector antes de quedarte con dashboards vacíos

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.