Install and configure Linkerd monitoring: NRDOT with manifest

Install

1. Add the Linkerd scrape config to the receivers.prometheus.config.scrape_configs list in your local deployment-configmap.yaml.

   - job_name: 'linkerd-controller'
     kubernetes_sd_configs:
       - role: pod
         namespaces: { names: ['linkerd', 'linkerd-viz'] }
     relabel_configs:
       - { source_labels: [__meta_kubernetes_pod_container_port_name], action: keep, regex: admin-http }
       - { source_labels: [__meta_kubernetes_pod_container_name], target_label: component }
       - { source_labels: [__meta_kubernetes_namespace], target_label: namespace }
       - { source_labels: [__meta_kubernetes_pod_name], target_label: pod }
   - job_name: 'linkerd-proxy'
     kubernetes_sd_configs: [{ role: pod }]
     relabel_configs:
       - { source_labels: [__meta_kubernetes_pod_container_name, __meta_kubernetes_pod_container_port_name, __meta_kubernetes_pod_label_linkerd_io_control_plane_ns], action: keep, regex: ^linkerd-proxy;linkerd-admin;linkerd$ }
       - { source_labels: [__meta_kubernetes_namespace], target_label: namespace }
       - { source_labels: [__meta_kubernetes_pod_name], target_label: pod }
       - { source_labels: [__meta_kubernetes_pod_label_linkerd_io_control_plane_ns], target_label: linkerd_control_plane_ns }
       - { source_labels: [__meta_kubernetes_pod_label_linkerd_io_control_plane_component], target_label: linkerd_control_plane_component }

   Copy

2. Add the processors and the metrics/linkerd pipeline to the same deployment-configmap.yaml.

   processors:
     resource/strip_service:
       attributes:
         - { key: service.name, action: delete }
         - { key: service.instance.id, action: delete }
     transform/k8s:
       metric_statements:
         - context: datapoint
           statements:
             - set(attributes["k8s.namespace.name"], attributes["namespace"]) where attributes["namespace"] != nil
             - set(attributes["k8s.pod.name"], attributes["pod"]) where attributes["pod"] != nil
             - delete_key(attributes, "instance")
     transform/deployment:
       metric_statements:
         - context: datapoint
           statements:
             - set(attributes["k8s.deployment.name"], attributes["k8s.pod.name"]) where attributes["k8s.deployment.name"] == nil and attributes["k8s.pod.name"] != nil
             - replace_pattern(attributes["k8s.deployment.name"], "-[a-z0-9]+-[a-z0-9]+$", "") where attributes["k8s.deployment.name"] == attributes["k8s.pod.name"]
     transform/metadata_nullify:
       metric_statements:
         - context: metric
           statements:
             - set(description, "")
             - set(unit, "")
     filter/drop_unused:
       error_mode: ignore
       metrics:
         metric:
           - 'name == "rustls_info" or name == "proxy_build_info"'
           - 'name == "scrape_series_added"'
           - 'IsMatch(name, "stack_(poll|create|drop)_total") or name == "stack_poll_total_ms"'
           - 'IsMatch(name, "tokio_rt_.*")'
           - 'IsMatch(name, "(inbound|outbound)_http_.*_frame_size_bytes")'
           - 'IsMatch(name, "(inbound|outbound)_tcp_detect_http_duration_seconds")'
           - 'IsMatch(name, "outbound_tcp_balancer_queue_.*")'
           - 'name == "scrape_duration_seconds" or name == "scrape_samples_scraped" or name == "scrape_samples_post_metric_relabeling"'
   
   pipelines:
     metrics/linkerd:
       receivers: [prometheus]
       processors: [memory_limiter, resource/strip_service, transform/k8s, transform/deployment, transform/metadata_nullify, filter/drop_unused, resource/newrelic, batch]
       exporters: [otlp_http/newrelic]

   Copy

3. Re-apply the ConfigMap and restart the collector deployment.

   bash

   Copy

   $
   kubectl apply -f rendered/deployment-configmap.yaml -n newrelic
   $
   kubectl rollout restart deployment -n newrelic

Find your data

1. Go to one.newrelic.com > All capabilities > All entities.
2. Search for your cluster name.
3. Select your Linkerd entity to open the built-in dashboard.

The built-in dashboard covers request rate, latency p50/p95/p99, success rate, TCP connections, mTLS certificate status, control plane health, and meshed pod inventory. For detailed information, refer to Find Linkerd data documentation.