Open litetex opened 2 months ago
Pinging code owners:
processor/resourcedetection: @Aneurysm9 @dashpole
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Crash the container when this happens so that it can get restarted automatically due to the restart policy
Maybe a new error_mode
configuration option like the transform processor would help, when set to propagate
it should return any detector error and crash the collector.
Another viable solution would be what is being proposed here: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34876
Component(s)
processor/resourcedetection, processor/resourcedetection/internal/docker
What happened?
Description
I'm running a container of this project with the resourcedetectionprocessor/docker.
The corresponding config looks like this:
After a system restart the resource detector loses it's functionallity (the lables from the docker host are no longer picked up) and the following message shows up in the log:
This is likely because docker is currently starting up.
Possible fixes:
It would be great to also make this configureable.
Collector version
v0.107.0
Environment information
Environment
Ubunut 24.04 LTS Docker CE 27.1.2
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response