Re: Prometheus & Observability documentation
toggle quoted messageShow quoted text
Thanks Arthur - those questions are an amazing indication for us what sections of our potential SIG 101 doc should be extended (:
> One topic that is still unclear to me is: When should I need tracing? You say that tracing is expensive and should be treated with care, so how do I know if tracing is worth for a particular case?
TL;DR the answer is simple: When other signals do not give the answer you are looking for (:
For example "why my request was slow? What part (e.g which service call) of the request execution was the bottleneck?" I find tracing definition by Peter Bourgon quite useful:
> (...) tracing then, is that it deals with information that is request-scoped. Any bit of data or metadata that can be bound to lifecycle of a single transactional object in the system. As examples: the duration of an outbound RPC to a remote service; the text of an actual SQL query sent to a database; or the correlation ID of an inbound HTTP request.
On Wed, 22 Jul 2020 at 01:12, Arthur Silva Sens <arthursens2005@...> wrote: