-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
K8sattributes unable to enrich pod,node, namespace labels and annotations in logs #34601
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I have checked this doc but not working for me. . |
Pinging code owners for processor/k8sattributes: @dmitryax @rmfitzpatrick @fatsheep9146 @TylerHelmuth. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
While deployed as Deployment it is working. But while deployed as Daemon set it is not working k8s annotations labels not enriching |
Hey @Praveen2099. The component that adds the labels and annotations is the In addition, you will need to share the details about the issue you are facing.
|
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. |
Component(s)
receiver/filelog
What happened?
Description
I have gone through different regex and other documents to enrich labels and annotations in the logs.so i want otel collector configuration to get all labels and annotations of pods ,nodes and namespace.
Steps to Reproduce
Expected Result
Actual Result
Collector version
0.106.1
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: