Chapter 13 – Driving Change
- Using a single backend for all signals has certain advantages. It should be easier to navigate between signals: for example, get all logs correlated with the trace, query events, and traces together with additional context, and jump from metrics to trace with exemplars. So, using a single backend would reduce cognitive load and minimize duplication in backend-related configuration and tooling.
Using multiple backends can help reduce costs. For example, it’s usually possible to store logs in a cheaper log management system, assuming you already have everything up and running for logs and metrics. But these backends don’t always support traces well. Adding a new backend for traces and events only would make total sense.
Tools such as Grafana may be able to provide a common UX on top of different backends to mitigate some of the disadvantages.
- There are a few things that we need to do:
- Lock down the context propagation...
