📂 DPS Cost Allocation Dashboard V1.2

[Erik_Anderssen]

Dear community members,

Please make sure you have read this documentation, before using the Cost Allocation Dashboard: https://docs.dynatrace.com/docs/manage/dynatrace-platform-subscription/cost-allocation

The DPS Cost Allocation dashboard allows you to view your current cost-field enrolment status, along with the usage and expenses associated with each supported capability. Use the top left section to navigate between different capabilities.

The variables in the top middle area enable you to adjust the pricing according to your rate card. 

You can use this Dashboard as a foundation to create your own usage and cost summaries, which can then be shared with your colleagues internally.

If you have any queries or suggestions for improvement, don't hesitate to share them by posting in this group.

[AntonPineiro]

Hi,

Thank you! 

Best regards

[AntonioSousa]

@Erik_Anderssen,
I was not able to upload it. Gave me the error: "Could not map JSON at 'tiles' near line 1 column 1584"

[Erik_Anderssen]

Hey @AntonioSousa!

I'm sorry you had problems with the Dashboard upload. We tested it in different settings and couldn't recreate the issue. I checked with the Dashboard team, but we need to investigate further. Can you contact our Support team to look into this?

[p_devulapalli]

Hi @Erik_Anderssen , I actually see dashboard returning empty results on my side. I was looking at the DQL used and see the  filter set as event.provider == "LIMA_CLIENT" . Looking at the event.provider info on my side I dont see this as a option to filter on . Am I missing something on my side please?

[p_devulapalli]

Ok, I just read your other thread, got some understanding 

https://community.dynatrace.com/t5/DPS-Cost-Allocation/Welcome-to-DPS-Cost-Allocation-What-is-it-Wha...

[Erik_Anderssen]

Hi @p_devulapalli Thanks for bringing this up - i adapted this article to point to the documentation first to make it clearer.

[paolo_fumanelli]

Hi Erik, thanks for sharing. I just tried to upload the dashboard on my tenant but provides actually no result. By digging into DQL I see that all data comes from events kind "BILLING USAGE EVENT" but when executing the DQL below:

fetch dt.system.events
| filter event.kind == "BILLING_USAGE_EVENT"
| summarize count(), by:{event.type}

you can see we have no event type related to host monitoring and in general for the capabilities included in the dashboard.

Do you know if there's anythiing I should activate to produce such events?

thanks
Paolo

[Erik_Anderssen]

Hey @paolo_fumanelli,

Please make sure that you have set the tags for cost allocation (dt.cost.costcenter, dt.cost.product). Here you can find more details: https://docs.dynatrace.com/docs/manage/dynatrace-platform-subscription/cost-allocation

Once you have set the tags it might take up to 30 minutes until you can see the first overviews appearing in the dashboard. 

Best regards

Erik

[paolo_fumanelli]

Thanks, I didn't get before that it was mandatory to set cost centers to get these events.

Thanks
Paolo

[earl_l_williams]

Hello Erik,

Is there a RFE to allow us to use current tags that we have for cost center and product?  We have tags with automations around these tags now and don't want duplicate tags to use this product.

Thanks,

Earl

[Sophie_Mayerw]

Hi Earl,
As of today, there is no way around explicitly setting those tags for on-premise hosts. However, there are possibilities for K8s. 
If this is of interest to you, please see:
https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/metadata-automation/k8s-metadata-tel...


If you're automation is based on automated tagging rules, then they can't be used for Cost Allocation. Cost Allocation tags need to be available on the OneAgent level. 

If your automation is working on the OneAgent level already: For most OneAgent scenarios, it's also possible to set environment variables that are then used for the OneAgent setup. This can help reduce the effort of changing an existing automation. 

HTH,

Sophie

[earl_l_williams]

Hello Sophie,

Thanks for the response.

I wanted to see if any other customers were asking to see if they can leverage other metadata variables for this DPS application, other than dt.cost.costcenter and dt.cost.product.  We currently have those same metadata values in our agents, but under different names.

Our application teams have been complaining to us about having duplicate metadata and tags, indicating that it increases complexity around knowing what value to use for dashboarding, data explorer, SLOs, etc.  They have been asking us to minimize the amount of duplicate metadata and tags when possible.

Do you know if there is an existing RFE or possibility that this is being coded now to allow us to use a different variable?

Thanks,

Earl Williams

[Sophie_Mayerw]

Hi Earl,

Thanks for the context!

You're right that dt.cost.costcenter and dt.cost.product are the only supported variables for DPS cost allocation today. I’m not aware of any active RFE or development to support alternative keys at the moment.

Totally hear you on the metadata duplication pain—others have run into similar challenges. If this is something your teams are actively struggling with, raising an RFE would be the best way to get it on the radar.

Best,
Sophie

[earl_l_williams]

Thanks @Sophie_Mayerw .   Just added this RFE:

https://community.dynatrace.com/t5/Product-ideas/DPS-Cost-Allocation-Use-of-customer-tags-and-not-ha...

[Viju111kammar]

Thanks for sharing..!