Remove Event field as it is causing issues with pre-trained source types #8039
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required for all PRs:
Description
I found that telegraf metrics export to splunk does not work on some of our environments. After all i found that reason was "event: metric" object in the json. To understand if it is needed here and why it works on some other environments i opened ticket to the vendor.
Summary of replies is:
event
field is not needed for the normal splunk metrics and it shoud work without it in all cases._json
orcollectd_http
) splunk would fail if this field is exists, probably due to more strict json checking.After this i decided to raise this PR to remove this field from the upstream. I tested it on my environments and it works fine.