[processor/k8sattributesprocessor] add debug logs

[povilasv]

Description:

Adding debug logs to k8sattributesprocessor - at the moment it is impossible to debug when the k8sattributeprocessor fails to add metadata. Adding debug logs for pod identification allows us to see the issue with pod association.

Link to tracking Issue:

Testing:

Tested locally:

Here are some examples of messages:

2022-06-10T07:08:12.818Z        debug   k8sattributesprocessor/processor.go:111 Evaluating Pod Identifier       {"kind": "processor", "name": "k8sattributes", "pipeline": "traces", "pod identifier key": "k8s.pod.ip", "pod identifier value": "10.244.0.179"}

2022-06-10T07:08:06.610Z        debug   k8sattributesprocessor/processor.go:111 Evaluating Pod Identifier       {"kind": "processor", "name": "k8sattributes", "pipeline": "metrics", "pod identifier key": "", "pod identifier value": ""}  

2022-06-10T07:08:12.818Z        debug   k8sattributesprocessor/processor.go:123 Getting the pod {"kind": "processor", "name": "k8sattributes", "pipeline": "traces", "pod identifier value": "k8s.pod.ip", "pod": {"Name":"jaeger-http-app-7f7c9657cd-h8rfb","Address":"10.244.0.179","PodUID":"293411d1-5132-46d0-aa6a-df138ca937aa","Attributes":{"":"jaeger-http-app","k8s.deployment.name":"jaeger-http-app","k8s.na
mespace.name":"sys-mon"},"StartTime":"2022-06-09T11:23:02Z","Ignore":false,"Namespace":"sys-mon","Containers":null,"DeletedAt":"0001-01-
01T00:00:00Z"}}       

Documentation: