You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
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: