One of Linkerd’s most powerful features is its extensive set of tooling around observability—the measuring and reporting of observed behavior in meshed applications. While Linkerd doesn’t have insight directly into the internals of service code, it has tremendous insight into the external behavior of service code.
Linkerd’s telemetry and monitoring features function automatically, without requiring any work on the part of the developer. These features include:
This data can be consumed in several ways:
Linkerd is not designed as a long-term historical metrics store. While Linkerd’s control plane does include a Prometheus instance, this instance expires metrics at a short, fixed interval (currently 6 hours).
Rather, Linkerd is designed to supplement your existing metrics store. If Linkerd’s metrics are valuable, you should export them into your existing historical metrics store.
See Exporting Metrics for more.