-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Feature] Simple docker container metadata? #18920
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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. |
I think this is a valid feature request for the docker detector. @rwjack, feel free to contribute if you're interested |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
processor/k8sattributes, processor/resourcedetection
Is your feature request related to a problem? Please describe.
Is there a way of gathering docker container metadata from
resourcedetection.detectors["docker"]
, such as container name, compose stack name, image name/tag?Something similar to the k8sattributes processor?
Describe the solution you'd like
A processor that collects basic docker metadata:
Describe alternatives you've considered
Using logsprout as per:
SigNoz/signoz#1597 (comment)
Additional context
No response
The text was updated successfully, but these errors were encountered: