jaeger

Not associated with the project but a quick look suggests: a database (clickhouse), alertmanager, query-service, frontend are signoz components, otel* and hotrod are for distributed tracing. Otel stands for open telemetry (https://opentelemetry.io/), hotrod is a tracing demo app from jaeger: https://github.com/jaegertracing/jaeger/tree/main/examples/h.... Without thinking too much about it, I assume that: hotrod is a demo data source pushing traces to the otel collector, which stores data in clickhouse. Frontend fetches data from clickhouse using the query service. Alert manager probably looks at traces coming in and detects anomalies, so that you can get real-time alerts when things don’t look normal.

Disclaimer: I work on OpenTelemetry spec. Many tracing solutions settled on 128bits/16 bytes trace ids. Here is Jaeger's rationale: https://github.com/jaegertracing/jaeger/issues/858 It is also recommended by W3C: https://www.w3.org/TR/trace-context/#trace-id

https://dzone.com/articles/distributed-tracing-with-zipkin-a... https://github.com/jaegertracing/jaeger' A quick search yielded these interesting projects.

At Uber we built Jaeger (https://github.com/jaegertracing/jaeger), which is doing something like 200K writes per minute into our Cassandra cluster.

Example golang multi-stage build: https://github.com/jaegertracing/jaeger/blob/master/cmd/quer...

The jagger logo is indeed awesome! (https://github.com/jaegertracing/jaeger)

This might be interesting to you: https://github.com/jaegertracing/jaeger/issues/425 The Dapper model is interesting, but Jaeger is not 100% based on that.