Monitored pod Kubernetes metadata enrichment
- Latest Dynatrace
- Explanation
- 2-min read
- Published Aug 25, 2026
The Extension Execution Controller (EEC) automatically enriches signals from extensions running on Kubernetes—metrics, logs, and events—with Kubernetes pod metadata.
How enrichment works
When an extension sends a signal, the device.address attribute identifies the monitored pod—the database or service pod the extension collects data from. The EEC resolves that pod from its local metadata cache and fills in the following attributes for the monitored pod's Kubernetes context, if not already set:
| Attribute | Description |
|---|---|
| Unique identifier of the cluster |
| Name of the cluster |
| Namespace the monitored pod belongs to |
| Name of the monitored pod |
| Unique identifier of the monitored pod |
| Node the monitored pod runs on |
| Name of the container within the monitored pod |
| Workload type, for example |
| Name of the workload managing the monitored pod |
Enable pod tracking
For the EEC to resolve a monitored pod, label that pod with extensions.dynatrace.com/metadata=true. The EEC skips pods without this label and forwards their signals without Kubernetes metadata.
Apply the label to the pods your extensions monitor:
metadata:labels:extensions.dynatrace.com/metadata: "true"
Extensions