Deep Linking Metrics and Traces with OpenTelemetry, OpenMetrics and M3
Metrics and traces are two pillars of Observability and are often used in a complementary fashion. Metrics can give you a high level view of applications responses and performance and tracing can giv …
| Talk Title | Deep Linking Metrics and Traces with OpenTelemetry, OpenMetrics and M3 |
| Speakers | Rob Skillington (CTO, Chronosphere) |
| Conference | KubeCon + CloudNativeCon North America |
| Conf Tag | |
| Location | San Diego, CA, USA |
| Date | Nov 15-21, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Metrics and traces are two pillars of Observability and are often used in a complementary fashion. Metrics can give you a high level view of application’s responses and performance and tracing can give you a detailed view of requests through applications. Often when using metrics in graphs or alerts you want be able to jump to an example of a request represented by a given metric datapoint which is difficult to do today. In this talk we show an example of this using an OpenTelemetry exporter to publish trace IDs as exemplars using the OpenMetrics exposition format.We then walk through configuring Jaeger as a tracing backend and M3 as a metrics backend to store the trace ID alongside a datapoint. We show how it is then possible to go from a metrics graph that visualizes the latency of your application to a trace that fell into a latency bucket using the deep link of the trace ID.
