-
Notifications
You must be signed in to change notification settings - Fork 5.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
Telegraf to Splunk [[outputs.http]] #11500
Comments
Hi, Thanks for taking the time to file an issue. There was one change to the splunk metric serializer I think in this time frame via #11237. This came from users of Splunk where they were expecting the "event" field. Do you think this is relevant to your use-case? Otherwise, it would be good to see if you could do the following:
Thanks! |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you! |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.23.2-1, Oracle Linux 8.6
Docker
No response
Steps to reproduce
...
Expected behavior
Metrics work on the downgraded version, same config. Not sure why 1.23.x is having an issue.
Actual behavior
Data appears to be sent.
Additional info
No response
The text was updated successfully, but these errors were encountered: