Component(s)
exporter/prometheusremotewrite
What happened?
Description
The PRW exporter reports all HTTP errors as error_permanent="true" on otelcol_exporter_send_failed_metric_points_total, including 5xx responses. Those are backend failures, not data errors, so you can't use error_permanent to tell the difference between the backend being down and a tenant sending out-of-order samples.
Steps to Reproduce
Set service.telemetry.metrics.level: detailed on a collector with a PRW exporter pointing at a backend that returns 5xx. Send any metrics through it. Check otelcol_exporter_send_failed_metric_points_total, error_permanent="true" regardless of status code.
Expected Result
error_permanent="false" for 5xx responses, error_permanent="true" for 4xx.
Actual Result
error_permanent="true" for everything.
Collector version
v0.152.0
Environment information
No response
OpenTelemetry Collector configuration
Log output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Component(s)
exporter/prometheusremotewrite
What happened?
Description
The PRW exporter reports all HTTP errors as
error_permanent="true"onotelcol_exporter_send_failed_metric_points_total, including 5xx responses. Those are backend failures, not data errors, so you can't useerror_permanentto tell the difference between the backend being down and a tenant sending out-of-order samples.Steps to Reproduce
Set
service.telemetry.metrics.level: detailedon a collector with a PRW exporter pointing at a backend that returns 5xx. Send any metrics through it. Checkotelcol_exporter_send_failed_metric_points_total,error_permanent="true"regardless of status code.Expected Result
error_permanent="false"for 5xx responses,error_permanent="true"for 4xx.Actual Result
error_permanent="true"for everything.Collector version
v0.152.0
Environment information
No response
OpenTelemetry Collector configuration
Log output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.