-
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
[processor/k8sattributes] Allow to extract metadata from other namespaces #36670
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Triage: Issue appears to be well specified and has necessary info. Moving to |
@sathieu I see what you're doing with the transform processor, but it isn't clear to me what you need to the k8sattributes processor to do. It is capable of extracting labels from namespaces, but currently only the namespace associated to the data. |
@TylerHelmuth I want to extract metadata associated with |
Ok ya, the k8sattributes processor does not currently support defining the namespace to extract data from for a given pod. At the moment it is able to associate that telemetry came from a pod came in namespace A, and then associate namespace A metadata with the telemetry. It cannot be told that telemetry coming from a pod in namespace A be associated with metadata from namespace B. |
Component(s)
processor/k8sattributes
Is your feature request related to a problem? Please describe.
We have a notion of tenant. The tenant name is a label attached to a namespace.
Like this:
We use this to set tenant using a
transform
:But this is not enough because we have some logs where the tenant should be extracted from a namespace which is not the pod namespace. For example we have ingress-nginx logs in the ingress-nginx namespace where the ingress namespace is found.
Here is what we tried:
Describe the solution you'd like
Currently k8sattributes does several things:
I want only step 6, extracting attributes for a namespace that is not necessarily a pod namespace.
Describe alternatives you've considered
Injecting into
k8s.namespace.name
and reverting after. This is hackish and I couln't get it to work.Additional context
No response
The text was updated successfully, but these errors were encountered: