ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to implement Jaeger Adaptive Sampling to automatically balance trace volume, ensuring high‑traffic endpoints don’t overwhelm storage while rare errors are still captured.
Learn how to configure Jaeger’s sampling policies—Probabilistic, Rate‑Limiting, and more—to keep trace volume under control while still capturing critical performance data in a production microservices environment.
Learn how to move Jaeger trace storage from in‑memory to Cassandra or Elasticsearch by updating only the collector configuration, keeping your instrumented services unchanged.
Configure Jaeger’s adaptive sampling to keep trace ingestion near a target rate. Step‑by‑step instructions, verification, and rollback options.
Learn how Jaeger’s adaptive sampling dynamically tunes per‑operation trace rates to hit a global TPS target while preserving visibility into errors and low‑traffic paths.
Configure Jaeger 1.x adaptive sampling to hold a steady traces-per-second target across hot and cold services, with verification steps, fallback behavior, and rollback.
Learn how to set up the OpenTelemetry Collector to receive OTLP traces and metrics and forward them to Jaeger, Prometheus, and Loki with proper batching, retry logic, and resource attribution. Follow a step‑by‑step guide, validate the pipeline, and recover from common issues.
High‑traffic services can flood Jaeger with spans. Remote sampling lets you set global, per‑service, and per‑operation rates centrally—without redeploying. Learn how to configure, verify, and trade‑off head‑based sampling versus tail‑based guarantees.
Stop losing critical error traces to random sampling. Learn how to implement Jaeger tail-based sampling to capture 100% of failures and latency outliers while controlling storage costs.
jaegertracing
cassandra
opentelemetry
prometheus