Cost Allocation Roadmap Updates Thread

[Sophie_Mayerw]

Hi, dear DPS Cost Allocation users,

I'll use this thread to keep you updated about our DPS Cost Allocation roadmap. 

Next planned DPS SaaS Capabilities to be supported by DPS Cost Allocation:

• CQ3'25 - Log Ingest
• CQ3'25 - Log Retain
• CQ3'25 - Log Retain with included Query
• CQ3'25 - Traces Ingest
• CQ3'25 - Traces Retain

Next planned configuration convenient features:

• CQ3'25 - AWS / Azure telemetry metadata enrichment for DPS Cost Allocation (similar to K8s telemetry metadata enrichment)

Next capabilities in priority, without a delivery date yet:

1. Metrics Ingest & Retain
2. Events Ingest & Retain

Feel free to provide you're feedback about the above-stated plans

Cheers,

Sophie

[Jamey_Price]

Sophie,

Does your team have plans to use the existing entity ownership metadata we're already enriching Dynatrace with as part of Cost Allocation configuration?

It is cumbersome to assign additional ownership metadata just to use the Cost Allocation feature today.  Pairing that with the need to explicitly list entities as valid targets for billing allocations further increases the complexity.  Because of these factors, we're using our own DQL queries to analyze and apportion this data, not Cost Allocation.

I look forward to hearing more about this feature as it evolves.

Jamey

[Sophie_Mayerw · Accepted solution]

Hi @Jamey_Price 

Quick answer: No, we will not support the ownership metadata.

More context: We did receive this question several times and investigated in this direction. But it won't be supported. There are ways which this information can be used for migration/initial setup (for example: request the owner via API from the host - push it via API as a new attribute to the OneAgent of the host)

Instead, we do focus on reusing K8s and Cloud Provider Tags/Labels/Namespaces to be reused for Cost Allocation. 

K8s: https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/metadata-automation/k8s-metadata-tel...

Cloud Provider: Will work similarly to K8s and will be coming in CQ3 this year. 

HTH,

Sophie

[Jamey_Price]

Thank you for the clear, concise answer!  It's always helpful to know the direction Dynatrace is heading so we can plan accordingly.

[JoSk]

Hi, we stumbled upon an issue that we cannot set a host tag/property for some hosts (in particular AWS Fargate containers with build-time injection). Now we tried to just add the tag via manual or automatic tagging to the host, but that doesn't seem to work.

Is this intended, will there be support for manual/automatic tagging of hosts? (knowing that removal from tags will result in missing data)

[Sophie_Mayerw]

Hi @JoSk!
It should work on AWS Fargate as on all our other supported platforms. Please check with support to identify the correct configuration. (e.g. environment variables)
Using auto-tagging rules or the tags you can set on the UI on hosts is not supported. Even though everything is called a "tag," those are two different kinds of tags. We need the ones directly on the OneAgent—those can be attached to our Cost Allocation feature and all the telemetry data as well. 

[e5696287]

HI Sophie,

We have certain use case with respect to Cost allocation for Kubernetes,

1. We have a leveraged cluster which is nothing but shared between multiple apps, say shared between App A, App B etc.
2. As per doc this tagging will be applied at Dynakube level which is nothing same across all nodes in that cluster.
3. Now here is the tricky part with leveraged cluster as we have multiple apps which can report under any of the nodes we won't be able to find its costing based on App reporting in node.
4. This is where it gives me usage of cluster not the apps in that cluster.

I had a quick call with Dermanuelian, Chris <chris.dermanuelian@dynatrace.com> and explained the use case, it would really helpful if we can have app level cost allocation details at cluster.

Thanks,
Shri