Closed evilr00t closed 3 weeks ago
Pinging code owners:
processor/transform: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley
See Adding Labels via Comments if you do not have permissions to add labels yourself.
@evilr00t this is likely a duplicate of https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32080. Can you try enabling the transform.flatten.logs
feature gate and then setting flatten_data: true
in the transformprocessor config?
Details here: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor#transformflattenlogs
@TylerHelmuth Thank you for the info, I've enabled feature flag and I'm checking logs now, will let you know soon if that helped.
EDIT: logs are consistent now, thank you once again @TylerHelmuth !
P.S. I was looking for similar issues but didn't know problem was with set() - thought I'd report it as the processor/transform 👍
Component(s)
processor/transform
What happened?
Description
Doing the transform some of the resources are being improperly set, using values from completely different log message.
Steps to Reproduce
I use journald logging for Docker with image tagging:
OTEL config:
Expected Result
docker_image & container name should be used from syslog_identifier but they have completely different values, replication is gone and api is used which is separate container and shouldn't be here?
Actual Result
It looks like some resources are leaked? This shouldn't happen...
Collector version
0.106.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response