Cost Allocation in Azure Container Apps (ACA) - supported?

[pt_A360]

Cost Allocation in Azure Container Apps (ACA) — Supported way to set dt.cost.costcenter and dt.cost.product?

We are actively using Dynatrace DPS Cost Allocation for:

• On-prem hosts (OneAgent-managed
• Azure VMs (OneAgent-managed)
• Kubernetes workloads (via pod annotations)

These environments correctly classify usage based on the documented cost tags:

• dt.cost.costcenter
• dt.cost.product

Use case: Azure Container Apps (ACA)
We also monitor several workloads running in Azure Container Apps using the OneAgent deployed inside the container image.
The agent reports data successfully; however:

• These ACA OneAgents cannot be managed via Deployment Status (expected for PaaS container environments).
• Therefore, we cannot set host tags (dt.cost.*) via UI or OneAgent configuration.
• We would like these ACA workloads to participate in DPS Cost Allocation the same way our VMs and on-prem systems do.

Is applying cost allocation supported for ACA?

[JoSk]

We have the same issue with AWS Fargate container. Customer application sits on an AWS ECS cluster but needs to be instrumented using build-time injection.

They already added configuration to add custom metadata/tags to the injected container. But this only adds local metadata to the process itself, like:

dt.cost.costcenter = XYZ
dt.entity.host_group = XYZ-prod-aws

But this information is not passed to the generated Host entity in Dynatrace and thus licensing information is still "unallocated" for almost 10% of the environment ...