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

Automatic tags on Kubernetes/OpenShift components with labels (pod, namespace, etc.)

DynaMight Pro
DynaMight Pro

The literal phrase in the documentation, says "Dynatrace automatically derives tags from your Kubernetes/OpenShift labels. This enables you to automatically organize and filter all your monitored Kubernetes/OpenShift application components." -- Organize Kubernetes/OpenShift deployments by tags | Dynatrace Docs

The requirements stated are:

  • Pods are monitored with a code module
  • automountServiceAccountToken: false isn't set in your pod's spec

However, with this requirements set, the Azure components like pods, containers, workloads, services and namespaces are not automatically tagged. Although labels are applied and visible in the properties details of the entities.

Oddly enough deriving process groups and services do get automatically [Azure] tagged.

Is this a configuration thing, or is the documentation not accurate? Are we missing a crucial tagging element?

I see several questions and RFE's similar to this topic, but it is not clear on this, and the  statement as documented.



Kind regards, Frans Stekelenburg                 Certified Dynatrace Associate |, Dynatrace Partner

DynaMight Legend
DynaMight Legend

Hoping we get clarity on this at perform. I have noticed the same, even when designing automatic tags you cannot target the namespaces, workloads etc.... We had to leverage the entity selector using relationalship statements to effectively tag the desired entities, but its not scalable for large organizations.