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
Is your feature request related to a problem? Please describe.
When using the Splunk HEC exporter, my app logs are shown like this but if I send my app logs in OTLP JSON format, they look like this. I want to see my app logs in OTLP JSON format so that I can get information such as severity text & number, the resource attributes, span id & trace id, etc.
Describe the solution you'd like
Add a JSON serialization option to transform data from OTLP format to OTLP JSON format
Describe alternatives you've considered
I was informed that Splunk doesn't support receiving logs in OTLP. If JSON serialization isn't viable, then perhaps supporting OTLP logs could be an alternative, so that you can see certain attributes like severity text & number and span id & trace id as its own field, instead of just host, source, and sourcetype.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
Splunk HEC exporter
Is your feature request related to a problem? Please describe.
When using the Splunk HEC exporter, my app logs are shown like this but if I send my app logs in OTLP JSON format, they look like this. I want to see my app logs in OTLP JSON format so that I can get information such as severity text & number, the resource attributes, span id & trace id, etc.
Describe the solution you'd like
Add a JSON serialization option to transform data from OTLP format to OTLP JSON format
Describe alternatives you've considered
I was informed that Splunk doesn't support receiving logs in OTLP. If JSON serialization isn't viable, then perhaps supporting OTLP logs could be an alternative, so that you can see certain attributes like severity text & number and span id & trace id as its own field, instead of just host, source, and sourcetype.
Additional context
No response
The text was updated successfully, but these errors were encountered: