Drop data during an interval of time after an unrecoverable export error

[iblancasa]

Component(s)

exporter/coralogix

Is your feature request related to a problem? Please describe.

We would like to improve the resilience and efficiency of the Coralogix exporter by introducing temporary data dropping behavior when specific persistent errors are encountered. The motivation for this change is to reduce unnecessary load on the Coralogix backend in scenarios where continued retries are futile or harmful, such as authentication failures or quota violations.

Describe the solution you'd like

Implement a mechanism in the Coralogix exporter that will:

Identify certain "hard failure" responses from the Coralogix backend, specifically:

• 401 Unauthorized or 403 Forbidden (indicating authentication/authorization failure)
• 429 Too Many Requests or other quota-related responses

Upon receiving one of these errors, suppress/delay further data exports for a fixed cooldown period, proposed to be 1 minute.

During this cooldown, all telemetry data should be dropped, not queued or retried.

This strategy aligns with best practices for exporters interacting with third-party services and helps reduce avoidable system strain.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for exporter/coralogix: @povilasv @iblancasa @douglascamata. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[github-actions]

Pinging code owners:

• exporter/coralogix: @povilasv @iblancasa @douglascamata

See Adding Labels via Comments if you do not have permissions to add labels yourself.