-
Notifications
You must be signed in to change notification settings - Fork 39
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
Sumo exporter should not send empty log body attributes #1169
Comments
Yeah, that looks like a bug. You can work around it by setting the Body to the empty string instead of deleting it. |
@swiatekm-sumo Is it possible that because of Nil we are seeing tons of below errors? Shouldn't 'transform/flatten' set the body to empty? or do we need to set it explicitly? If yes, how to do it? |
That sounds like an issue in https://github.com/SumoLogic/sumologic-kubernetes-collection. Can you file it there with the configuration you're using? |
@swiatekm-sumo I still faces the same issue- |
@rupeshnemade can you add a logging processor to your configuration with |
@swiatekm-sumo Attaching the log file |
This is actually a bug in filelog receiver. The body in your record is actually a nonempty string with the value Can you file this bug upstream? |
I have opened a bug open-telemetry/opentelemetry-collector-contrib#24017 |
When we removes body from the logs with filelog receiver and tries to forward it with Sumo exporter then Sumo renders the key value as Nil.
It's expected that if the value is Nil then key should not appear at all.
This code logic needs to be updated to not send blank values.
The text was updated successfully, but these errors were encountered: