ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
The OpenTelemetry Collector operates as a stateless intermediary, exporting telemetry via OTLP to various storage backends like ClickHouse or Prometheus. While the collector handles data buffering and retry logic, it lacks native mechanisms to verify the integrity of data sets after a backend-side backup restoration has occurred. Because the collector typica
Goal: Determine why the Jaeger Collector reports "spans dropped" metrics when the system is under concurrent request load. The Collector ingests spans via UDP or HTTP, buffers them, and writes to a backend such as Cassandra or Elasticsearch. Under high traffic, memory pressure or increased backend latency can cause the internal buffer to overflow, leading to
jaegertracing
opentelemetry