-
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
[receiver/k8sobject] request giving a option to use raw json object to represent k8s object #25857
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/k8sobjects: @dmitryax @hvaghani221. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@Frapschen, what's the problem you are trying to solve here? It doesn't seem like a receiver concern but rather a serialization of the file exporter. |
Why it currently cannot be parsed by fluentbit? |
I try to get the raw event object JSON data instead of OTLP JSON data in the log body. it's more like the file exporter concern indeed. |
I use this data flow to transport event data:
the fluentbit side will output this error log:
After I use Vector to replace the fluenbit in this data flow, I found that the Vector is working fine and I can confirm this is a fluenbit bug fluent/fluent-bit#7840. |
if we consider saving the event data into a file and using other tools like fluentbit |
I agree with @dmitryax that this is not a receiver concern. According to the OTel Logs specification, I also agree that it is wrong that the fileexporter is "leaking" our internal data model. It doesn't feel right that the fileexporter is printing the pdata structures, I think it should be printing a generic |
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. |
After some research, I think we can reuse the current |
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. |
with #31774 merged, we can use |
I use fileexporter with
|
Is |
Component(s)
receiver/k8sobjects
Describe the issue you're reporting
As an example of the event watcher, the receiver uses the map to represent the event object:
opentelemetry-collector-contrib/receiver/k8sobjectsreceiver/unstructured_to_logdata.go
Lines 75 to 78 in 919e970
this result taht the event JSON format will be like(use file exporter):
after structure, its body looks like this:
I expect the body just contain the raw event json object which can easy parse by downstream componment like fluenbit and friendly for storage .etc.
I have not context to know why use map but I suggest that we can have option to control it wheather using map or raw json.
I can sent a PR to imporve it.
The text was updated successfully, but these errors were encountered: