-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Align malformed data handling with splunkd #36096
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sure, do you want to work on this? |
Hey @atoulme . This seems like a lower priority item so we don't have to work on it yet. Can we keep this up for tracking purposes? We might get to it one day when this becomes more urgent. |
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)
receiver/splunkhec
Is your feature request related to a problem? Please describe.
When ingesting data into splunkhecreceiver via
/services/collector/event
endpoint, the behavior is different than splunkd if the payload is malformed.For example:
payload:
splunkhecreceiver accepts the data but has significant payload difference
splunkd would return
No Data
with code5
Describe the solution you'd like
align the behavior of splunkhecreceiver if the data is malformed. Return response of
{"text":"No data", "code":5}
insteadDescribe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: