Trace Completion Rate Degradation

critical

reliabilityUpdated Feb 7, 2026

When the ratio of saved traces to received spans drops below 95%, traces are being lost before storage, indicating storage backend issues, network timeouts, or collector resource constraints.

Sources

Troubleshooting | Jaegerwww.jaegertracing.io

Troubleshootingdevelopers.openai.com

Performance Tuning Guide | Jaegerwww.jaegertracing.io

Frequently Asked Questions | Jaegerwww.jaegertracing.io

Jaeger Monitoring: Essential Metrics and Alerting for Production ...last9.io

Jaeger Metrics: Internal Operations and Service Performance ... - Last9last9.io

Technologies:

JaegerSymptoms of this issue are visible in Jaeger metrics and logs

ElasticsearchThe root cause of this issue originates in Elasticsearch

CassandraThe root cause of this issue originates in Cassandra

How to detect:

Calculate the ratio of traces saved to spans received. If this completion rate falls below 95%, traces are being dropped. Monitor for sustained degradation over 2+ minutes.

Recommended action:

Investigate storage backend write latency and capacity. Check network connectivity between collectors and storage. Review collector CPU and memory limits. Verify sampling configuration isn't inadvertently dropping traces.