• /
  • EnglishEspañolFrançais日本語한국어Português
  • ログイン今すぐ開始

Linkerd OpenTelemetry metrics reference

|View as Markdown (English)

The Linkerd OTel integration collects metrics by scraping the Linkerd proxy admin port (:4191) and control plane pods using the OpenTelemetry Collector's Prometheus receiver.

HTTP traffic metrics

Emitted by every meshed pod's linkerd-proxy sidecar.

TCP metrics

Authorization metrics

Identity and mTLS metrics

Control plane metrics

Emitted by Linkerd control plane pods (destination, identity, proxy-injector).

Process metrics

Standard Prometheus process metrics emitted by each proxy.

Default-off metrics

The following metric groups are disabled by default in the optimized collector config to reduce ingest volume. Remove the corresponding condition from filter/drop_unused to re-enable.

ヒント

These groups are off by default because they provide no operational value in steady state. Enable them only when actively debugging the specific issue described.

Resource attributes

These attributes are added to every metric by the OTel Collector and can be used as FACET or WHERE filters.

Common attributes

Linkerd-specific attributes

kube-state-metrics attributes

These attributes are added only to metrics scraped from kube-state-metrics.

Linkerd distributed tracing with OpenTelemetry

Enable proxy trace export and instrument your application pods to correlate mesh spans with APM traces.

Collect Linkerd proxy logs

Optionally collect linkerd-proxy sidecar container logs.

Find and query your data

Dashboard walkthrough, NRQL queries, and troubleshooting steps.

Copyright © 2026 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.