-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Unable to extract k8s.container.name
and use as a Resource Attribute
#31509
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
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
In order to extract |
Hello @TylerHelmuth Thanks for that. I can see that However, I added it into my config as a test, and it then caused an error;
Is there something specific I need to do for this, or where to add it? Thanks |
I got mixed up on what you wanted to extract. In order to extract |
Thanks @TylerHelmuth I believe it is from what I can see, but not 100% certain. How could I verify this please? Thanks |
Remove the k8sattributesprocessor and then add a debugexporter with |
Hello @TylerHelmuth Thanks for that, yes they do have a |
If you inspect your pod does that container.id match the real container id? |
Thanks @TylerHelmuth No, the debug exporter shows an ID that I cant correlate to anything; But the k8sproccessor does show the correct
|
It looks like the incoming metrics/logs have a |
Thanks. The Service is the AdService from the OpenTelemetry Demo, however the logs show that the k8sproccesor does have the right container ID, if thats the case, should it not be able to add the Container Name attribute, or does it still defer to the Metric? |
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
What happened?
Description
I am unable to extract
k8s.container.name
and use as a Resource Attribute in my Telemetry dataSteps to Reproduce
Deploy OpenTelemetry Collector on Kubernetes (I am using GCP)
Deploy the OpenTelemetry Demo
Set the
k8s.container.name
andcontainer.id
to be extracted in thek8sattributes
processorObserve that the
k8s.container.name
is not there as a resource attributeExpected Result
The
k8s.container.name
should be a Resource AttributeActual Result
The
k8s.container.name
is not available as a Resource AttributeCollector version
0.93.0
Environment information
Environment
Kubernetes on GCP,
1.27.8-gke.1067004
OpenTelemetry Collector configuration
Log output
Additional context
I dont see the Attribute when setting the Debug Exporter.
I can see in the logs its able to extract the Container ID and Container Name.
The text was updated successfully, but these errors were encountered: