You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are running the OTel collector to gather logs from a docker containers on a docker host. The docker resource detection processor only gives you the following.
Name
Description
Values
Enabled
host.name
The host.name
Any Str
true
os.type
The os.type
Any Str
true
based on this document. We need additional container metadata to segregate logs.
I think this request is quite valid. From what I can understand the docker resource detector so far aims on host related attributes so not sure if container related metadata would fit there. I would lean towards creating a standalone dockerattributesprocessor component as it was suggested.
What container ID would we be fetching here? The Collector one? The purpose of the resourcedetection processor, as I understand it, is to populate the resource from the environment that the Collector is running on. If these attributes are about the Collector, then it would make sense to add them, but if they refer to other containers, then I don't think it makes much sense
Component(s)
processor/resourcedetection, processor/resourcedetection/internal/docker
Is your feature request related to a problem? Please describe.
We are running the OTel collector to gather logs from a docker containers on a docker host. The docker resource detection processor only gives you the following.
based on this document. We need additional container metadata to segregate logs.
Describe the solution you'd like
The resource detection processor adds:
Similar to what's implemented in Filebeat.
Describe alternatives you've considered
Alternate would be a
dockerattributesprocessor
like k8sattributesprocessor to enrich the logs with additional metadata.Additional context
No response
The text was updated successfully, but these errors were encountered: