Open swar8080 opened 4 months ago
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity. Please apply keepalive label to exempt this Issue.
Describe the bug
Tempo seems to use
429
status codes for requests that will not succeed with retries. For example, when the request payload size exceeds a maximum. Some clients retry on429
so this can cause in-memory export queues to fill-up when all retries are exhausted. Specifically, we are pushing spans to grafana cloud tempo using OTLP gRPC from an OpenTelemetry collector, which retries on429
sExpected behavior When retrying the same request will always fail then consider using a different status code, like 413 Payload Too Large.
Environment: OpenTelemtry Collector 0.96.0 -> Grafana Cloud Tempo
Additional Context These are the errors we hit from the OTEL collector: