4 Commits (258f8267477f9c4d1d950a6a0887c7a902af05ff)

Author	SHA1	Message	Date
Salva Corts	620488656f	Set tracing.profiling-enabled to true by default (#12004)	1 year ago
Cyril Tovena	5517eaa1b8	feat: Add tracing integration to profiling. (#11633) ... Same as https://github.com/grafana/tempo/pull/3276 this adds profiling integration to tracing instrumentation allowing to get profile for a single request removing the noise of everything else.	1 year ago
Pablo	5f665651d5	Promtail: Add basic tracing support (#7414) ... We've been using Promtail's HTTP/gRPC server-based targets with real workloads for some weeks now. The server that these spin out is based on [weaveworks commons](https://github.com/weaveworks/common) HTTP/gRPC servers. These include by default some middlewares that if enabled, inject tracing support. We found this useful when tracking down request handling time, or even more, if the caller also support Jaeger tracing support, cross-correlated requests between the upstream server and Promtail's. This PR adds support for enabling tracing the same way Loki does. At the moment, this will just generate traces for the before-mentioned targets. In the future, the quality and completeness of tracing support can grow organically to enrich spans.	3 years ago
Periklis Tsirakidis	6e55277552	Add flag to disable tracing (#2191)	5 years ago