/ 
Linkerd (OpenTelemetry Collector)

Linkerd (OpenTelemetry Collector)

Monitor Linkerd service mesh with OpenTelemetry for complete visibility into proxy health, request rates, latency, mTLS certificate lifecycle, and control plane performance using open-source, vendor-neutral instrumentation.

Quickstart
Integration Features

dashboards
Linkerd (OpenTelemetry Collector) quickstart contains 1 dashboard. These interactive visualizations let you easily explore your data, understand context, and resolve problems faster.
See all

Why monitor Linkerd using OpenTelemetry?

Linkerd is a lightweight, security-focused service mesh for Kubernetes that provides mTLS, observability, and traffic management for microservices. Monitoring Linkerd with OpenTelemetry gives you vendor-neutral, standardized visibility into the health and performance of your service mesh and every workload running inside it.

OpenTelemetry is an open source observability framework that provides IT teams with standardized protocols and tools for collecting and routing telemetry data. Organizations adopting OpenTelemetry gain the advantage of vendor neutrality by using flexible and open-source agents and collectors.

New Relic provides OpenTelemetry observability for Linkerd, ingesting comprehensive metrics from the Linkerd proxy sidecars, control plane components (destination, identity, proxy-injector), and Kubernetes workloads. This enables you to monitor service health, track request rates and latency, analyze mTLS certificate lifecycle, and troubleshoot performance issues across your entire mesh.

This quickstart gives you full observability into your Linkerd service mesh in minutes, whether your cluster is self-hosted or running on EKS, GKE, or AKS.

Linkerd (OpenTelemetry) quickstart highlights

Included in this quickstart you will find:

  • Instructions to install our Linkerd monitoring with OpenTelemetry.
  • Comprehensive dashboards tracking:
    • TCP connections and bytes transferred
    • Inbound and outbound HTTP request rates
    • Success rate and error rate per deployment
    • Request latency (p50/p95/p99) per deployment
    • mTLS certificate expiry and refresh rate
    • Control plane health (live endpoints, queue depth, request rate)
    • Proxy memory and CPU usage
    • Meshed pod inventory by namespace and deployment
    • Operations by service (service topology map)
  • Guided alert creation recommendations for:
    • High inbound request latency
    • Elevated HTTP error rate
    • Excess TCP connections

New Relic + Linkerd + OpenTelemetry = Complete service mesh observability

Monitor your Kubernetes service mesh with open-source instrumentation that provides vendor neutrality while delivering comprehensive insights into every proxied workload. Track golden signals, mTLS health, control plane performance, and service topology using standardized OpenTelemetry collectors paired with New Relic's powerful visualization and alerting capabilities.

How to use this quickstart

  • Sign Up for a free New Relic account or Log In to your existing account.
  • Click the install button.
  • Install the quickstart to get started or improve how you monitor your environment. They're filled with pre-built resources like dashboards, instrumentation, and alerts.
Authors
New Relic
Support
BUILT BY NEW RELIC
Need help? Visit our Support Center or check out our community forum, the Explorers Hub.
Collaborate on this quickstart

Starten Sie noch heute kostenlos

Derzeit ist diese Seite nur auf Englisch verfügbar.