-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[exporter/splunkhec] Support partial resends #36113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/splunkhec
Is your feature request related to a problem? Please describe.
The splunk_hec exporter doesn't support partial acceptance of records sent to the backend. The Splunk backend can offer information on how many events it was able to process before sending an error. A typical HTTP response body is:
The
invalid-event-number
key indicates when the payload processing stopped, for example 10 means that it stopped on the 10th one, and we can try resending by dropping the first 9 events.Describe the solution you'd like
Implement support to read the response, even on 503, and make sure to drop events if possible based on the feedback from the server.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: