Question 1

How to deploy Jaeger on Kubernetes?

Accepted Answer

Use the Jaeger Operator or Helm charts from the documentation; it automates setup of collectors, query services, and storage backends like Elasticsearch for scalable tracing in clusters.

Question 2

Jaeger vs Zipkin: which is better for microservices?

Accepted Answer

Jaeger has better OpenTelemetry integration and a more modern UI, while Zipkin is simpler but less feature-rich; choose Jaeger for cloud-native stacks requiring standardized instrumentation.

Question 3

What's the performance overhead of Jaeger tracing?

Accepted Answer

Sampling strategies like head-based reduce overhead, but instrumenting all requests can add latency; tail-based sampling in production helps minimize impact while capturing critical traces.

Question 4

How to send traces from a Node.js app to Jaeger?

Accepted Answer

Use the OpenTelemetry JavaScript SDK with OTLP exporter; configure it to point to the Jaeger collector's gRPC or HTTP endpoint on ports 4317 or 4318.

Question 5

Can Jaeger work with serverless functions like AWS Lambda?

Accepted Answer

Yes, but it requires configuring the OpenTelemetry SDK for short-lived functions and sending traces to a centralized Jaeger instance, which may need adjustment for cold starts.

Question 6

Does Jaeger support alerting on trace data?

Accepted Answer

Not natively; Jaeger focuses on visualization and querying, so you need to integrate with external monitoring tools like Prometheus or Grafana for alerts based on trace metrics.

jaeger

What is jaeger?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions