You can use Cost Allocation to allocate your Dynatrace Platform Subscription (DPS) usage to the cost centers and products that you define.
Allocating costs provides a transparent and detailed account of the Dynatrace expenditures that originate from each cost center or product, which in turn helps your organization optimize its budgets. Cost Allocation works with business events regardless of how they're captured.
On this page, you'll learn how to set up Cost Allocation for business events.
For business events, you can allocate costs related to ingest and query consumption.
We recommend setting up Cost Allocation along organizational lines and deployment scopes.
Suitable concepts include the entities that Dynatrace automatically associates with a business event (hosts, process groups, process group instances), and any custom business attributes already present in your payload, such as a department or event.provider field.
To add Cost Allocation information to your business events, enrich your records with the dt.cost.costcenter and dt.cost.product Grail attributes.
Depending on how your business events are produced, there are different ways to allocate your costs. Our recommendations are:
With ingest enrichment, you can create rules to automatically enrich all ingested business event signals with dt.cost.costcenter and dt.cost.product.
The data is stored in Grail:
Dashboards,
Notebooks, Account Management, and the Dynatrace API.For more information about enriching on ingest, see Configure ingest enrichment rules.
You can define Cost Allocation at the source via OneAgent, Kubernetes labels or annotations, or OpenTelemetry.
This lets you use your existing labels and tags, so that dt.cost.costcenter and dt.cost.product are already present when your data arrives.
If you only need to allocate costs at a coarse level of granularity, such as by event provider, you can use OpenPipeline to
Do this in the Cost allocation and Product allocation stages in OpenPipeline.
event.provider or a custom attribute like department.dt.cost.costcenter) or the Product allocation stage (to set dt.cost.product).For the full list of parameters and processor examples, see Cost allocation via OpenPipeline.
If you have a more sophisticated strategy for cost center tags, it might not be enough to map a single field directly to dt.cost.costcenter or dt.cost.product.
In this case, we recommend that you use a DQL processor in OpenPipeline to derive cost centers or products from a combination of fields, and then set dt.cost.costcenter or dt.cost.product from the resulting field with the Cost allocation stage. For examples, see OpenPipeline processing examples.
Before you change the values of dt.cost.costcenter or dt.cost.product, make sure they're defined in the Cost Allocation allow lists.