-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Consider moving Splunk HEC encoding out of Splunk HEC receiver and Splunk HEC exporter into an extension #30553
Comments
Pinging code owners for exporter/splunkhec: @atoulme @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/splunkhec: @atoulme. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Removing |
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 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. |
Most likely if we land this encoding extension, we will do it separately from the exporter as it right now has multiple tricks in place to enhance performance. We can close this issue as not planned. |
Component(s)
No response
Describe the issue you're reporting
Under
extensions/encoding
, we now have extensions that specify encodings that can be used by components. The HEC format can be parsed and marshaled to pdata as evidenced by the hec receiver and exporter.The work would probably go into multiple steps by identifying easiest targets first, most likely traces and receiver first.
The text was updated successfully, but these errors were encountered: