-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[exporters/otlphttpexporter] Support for json_log_encoding extension #36203
Comments
/label extension/encoding/jsonlogencoding |
/label extension/encoding |
Pinging code owners for extension/encoding: @atoulme @dao-jun @dmitryax @MovieStoreGuy @VihasMakwana. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@Frapschen do you have any ideas? |
Did you face any errors? |
@VihasMakwana The extension starts fine, don't see any errors even later:
but the result is like it is unaffected whether the extension is enabled or not. |
@mishranant I opted for the file exporter instead and used Fluent Bit to scrape the data and forward it to the backend. |
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. |
Component(s)
extension/encoding/jsonlogencoding
Is your feature request related to a problem? Please describe.
My use-case is to get data from the Kubernetes API, the data I am receiving on http endpoint is like so:
I want to get the raw event object JSON data instead of OTLP JSON data in the log body. Referring to this issue, I added json_log_extension in my config_map:
But that did not help at all. What could be the issue?
Describe the solution you'd like
If support for json_log_encoding is missing, would request it to be added.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: