Bubbling up meaningful information
As we’ve seen, capturing both out-of-the-box and custom telemetry can be done with relatively little effort. The real effort is paring down that information to ensure there is not too much noise, and that relevant information on the health and performance of an application is what gets brought to the top. This will save not only the patience of those who monitor the application but can also result in a lowered cost in storage and processing by limiting the volume of information stored.
To help illustrate, we will be using two examples of exporters that are compatible with OpenTelemetry – Prometheus and Jaeger:
- Prometheus is a popular time-series database commonly used with Kubernetes to capture both standard and custom telemetry for applications. Information is typically scraped (read from an endpoint) into the Prometheus database and retained for a finite period. This information can then be used in trend analysis to identify...
