Jaeger

Зачем

Networking
Качество архитектуры Наблюдаемость Observability
- Tracing
- Metric
  - Service Performance Monitoring (SPM) - Experimental Distributed context propagation Distributed transaction monitoring Root cause analysis Service dependency analysis Performance / latency optimization

Плюсы:

OpenTelemetry (OTel) Protocol
gRPC support
OpenSource
Хранилища
- ClickHouse
  - plugin gRPC
- PostgreSQL with Promscale, ELK
Topology Graph
- System Architecture
- Deep Dependency Graph
All Jaeger backend components expose Prometheus metrics by default (other metrics backends are also supported).
Logs are written to stdout using the structured logging library zap.
Service Performance Monitoring (SPM)
Visualizes aggregated span data in the form of RED (Requests, Errors, Duration) metrics to highlight services and/or operations with statistically significant request/error rates or latencies, then leveraging Jaeger’s Trace Search capabilities to pinpoint specific traces belonging to these services/operations.

Минусы:

Limitations
If your application exports both traces and metrics using OTLP, then you would still need to run the OpenTelemetry Collector, because the Jaeger collector can only accept the tracing portion of OTLP data. Alternatively, you may configure the SDK with two OTLP exporters pointing to different backends.
Not all the options supported by the OTLP receiver in the OpenTelemetry Collector are supported by the Jaeger backend.
Only the Jaeger collector supports the new OTLP receiver. The Jaeger agent only supports the “classic” Jaeger formats. If your deployment requires a local agent, we recommend running the OpenTelemetry Collector in that capacity.