cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Kubernets app only pod logs delivered via ingest api - association with dynatrace entities

PetrVlacil
Observer

Hello

Our client has a dynatrace managed. We monitor production OpenShift in CloudNative Fullstack. But for the dev OpenShift cluster we use App Only mode. To get container output logs to Dynatrace it is suggested to use for example fluentbit. If I understand it correctly with recommended default fluentbit config logs delivered via log ingest api should be associated with the monitored entities in the Dynatrace. However our client uses Vector. We are able to get the container output logs to Dynatrace using vector's http output sink but logs are not associated with the cluster/namespace/pod.

 

Vector is sending some of the kubernetes metadata with the logs. Currently we have:

k8s.container.name
k8s.namespace.name
k8s.container.image.name
k8s.container.id
k8s.pod.name

k8s.node.name

k8s.cluster.name

dt.kubernetes.cluster.name
host.name


But in fluentbit example value.yaml config mentioned in the Guide,  there are some more fields:
k8s.pod.uid
k8s.cluster.uid

dt.kubernetes.cluster.id

 

Does anyone know which information/metadata is Dynatrace exactly using to correlate api ingested logs with monitored entities? If vector starts sending k8s.pod.uid, k8s.cluster.uid, dt.kubernetes.cluster.id will the Dynatrace be able to assign the logs to entities or is any other information needed? For example does the Vector need to send also some pod annotations/labels that Dynatrace operator adds to Kubernetes objects?

 

Thank you and best regards

Petr

0 REPLIES 0

Featured Posts