ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use Jaeger’s probabilistic and rate‑limiting sampling to keep observability high while controlling storage, and see a concrete example that shows how to configure and verify the settings.
Learn how Jaeger's adaptive sampling automatically tunes trace collection to keep storage costs low while preserving visibility of slow or error requests.
Stop overloading your storage with redundant traces. Learn how to use Jaeger's probabilistic sampling to maintain system visibility while drastically reducing observability overhead.
Jaeger offers constant, probabilistic, rate-limiting, and adaptive sampling. Here's how to choose between them, verify what clients actually received, and when you need tail sampling instead.
Stop choosing between storage crashes and missing traces. Learn how Jaeger's Adaptive Sampling dynamically adjusts trace rates to balance observability with operational costs.
Goal Develop a test harness for a Jaeger client that can be run in CI or local environments without using real production credentials. Constraints and Uncertainty The Jaeger client library expects an authentication token or basic auth header when sending spans to a secured collector. Using production credentials in tests is forbidden by policy, yet the colle
Goal The Jaeger Collector exposes a gRPC server whose concurrent stream capacity is controlled by the grpc-server.max-concurrent-streams setting. When bursts of span ingestion exceed this limit, the collector may queue or reject new streams, leading to intermittent connection pool exhaustion that manifests as client reconnection storms. Uncertainty However,
Assume a Jaeger Operator deployment using the v1 CRD API and a Jaeger 1.x collector; the exact Operator, Jaeger, and Kubernetes or OpenShift versions remain to be confirmed. The integration boundary is the collector’s health-check interface and the cluster’s probe implementation. HTTP probes, native gRPC probes, and Operator-managed probe fields are not nece
Span Ingestion Timeout Configuration The Jaeger Collector handles span ingestion from agents and services, with configurable timeout settings that determine how long the collector waits for storage operations to complete. When the underlying storage backend undergoes schema changes—such as Elasticsearch index template updates or Cassandra schema migrations—t
jaegertracing
opentelemetry
grpc