Jaeger
An open-source distributed tracing system, originally released by Uber and donated to the CNCF. It supports storage, visualization and analysis of OpenTelemetry data.
Timeline (last 90 days)
n8n traces can be exported to any OTLP-compatible collector and backend, and the officially listed supported targets include Jaeger, Tempo, Datadog, Honeycomb, New Relic, and Grafana Cloud.
AI网关通常充当反向代理或SDK包装器，其数据流大致为：网关接收入站HTTP请求并创建根span，随后为具体操作创建子span（如`retrieval.search`、`llm.inference`、`llm.generate`），span通过OTLP批量导出到collector，再路由到Jaeger或Tempo进行存储与可视化。
Microsoft Foundry follows the OpenTelemetry standard, and Traces data can theoretically be exported to OpenTelemetry-compatible backends such as Jaeger and Grafana Tempo.
Traces from chip-level hardware counter data are at a finer granularity than information from distributed tracing tools such as OpenTelemetry and Jaeger.
Major cloud vendors including Google, Microsoft, and AWS all support OpenTelemetry, and tracing data built on it can be exported to compatible backends such as Jaeger, Zipkin, and Grafana Tempo.
Telemetry data generated by OTEL can be forwarded via a Collector to Jaeger, Prometheus, Datadog, or any backend compatible with the OTLP protocol
Jaeger and Zipkin are distributed tracing tools that can display the complete latency and call relationships of requests across multiple service nodes.
The core value of OpenTelemetry lies in its vendor neutrality, allowing telemetry data to be exported to backends such as Jaeger, Zipkin, Datadog, and Grafana Tempo
Tail-based sampling in distributed tracing systems first caches all spans for a request, and only decides whether to retain them after the entire trace is complete.
Mainstream observability backends including Jaeger, Grafana Tempo, Datadog, New Relic, and Elastic all support direct ingestion via the OTLP protocol.
2 more timeline events
All Facts (13)
SkyWalking和Jaeger是链路追踪工具，用于全链路性能测试中的分布式系统追踪
90%Unverifiedn8n traces can be exported to any OTLP-compatible collector and backend, and the officially listed supported targets include Jaeger, Tempo, Datadog, Honeycomb, New Relic, and Grafana Cloud.
50%UnverifiedAI网关通常充当反向代理或SDK包装器，其数据流大致为：网关接收入站HTTP请求并创建根span，随后为具体操作创建子span（如`retrieval.search`、`llm.inference`、`llm.generate`），span通过OTLP批量导出到collector，再路由到Jaeger或Tempo进行存储与可视化。
50%UnverifiedMicrosoft Foundry follows the OpenTelemetry standard, and Traces data can theoretically be exported to OpenTelemetry-compatible backends such as Jaeger and Grafana Tempo.
50%UnverifiedTraces from chip-level hardware counter data are at a finer granularity than information from distributed tracing tools such as OpenTelemetry and Jaeger.
50%UnverifiedMajor cloud vendors including Google, Microsoft, and AWS all support OpenTelemetry, and tracing data built on it can be exported to compatible backends such as Jaeger, Zipkin, and Grafana Tempo.
50%UnverifiedTelemetry data generated by OTEL can be forwarded via a Collector to Jaeger, Prometheus, Datadog, or any backend compatible with the OTLP protocol
50%UnverifiedJaeger and Zipkin are distributed tracing tools that can display the complete latency and call relationships of requests across multiple service nodes.
50%UnverifiedThe core value of OpenTelemetry lies in its vendor neutrality, allowing telemetry data to be exported to backends such as Jaeger, Zipkin, Datadog, and Grafana Tempo
50%UnverifiedTail-based sampling in distributed tracing systems first caches all spans for a request, and only decides whether to retain them after the entire trace is complete.
50%UnverifiedMainstream observability backends including Jaeger, Grafana Tempo, Datadog, New Relic, and Elastic all support direct ingestion via the OTLP protocol.
50%UnverifiedObservability practices are implemented through tools such as the OpenTelemetry standard, Prometheus metrics collection, and Jaeger/Zipkin distributed tracing.
50%Unverified分布式追踪系统Jaeger默认只采样0.1%的请求
50%