With Cost Intelligence, you can move from a billing number to a root cause and on to concrete optimization steps by asking questions instead of writing DQL. Dynatrace Assist will translate your prompts into queries and execute them on its own.
In this guide, you will:
This guide is written for:
You don't need to have any prior DQL knowledge or experience to follow this guide, since Assist can translate natural language into queries and execute them.
Most teams know how much they spent on observability, but it can be difficult to explain the reason behind the spending (which capability, which team, or which workload drove the change) or decide what to do about it. Dynatrace Platform Subscription (DPS) spans many capabilities and signal types, and investigating a root cause from a billing number has traditionally required manual analysis and a working knowledge of DQL.
Cost Intelligence closes that gap. It pairs the Dynatrace data foundation of granular, real-time usage and billing data in Grail with the expertise built into Dynatrace Assist.
This allows you to answer cost questions across three core scenarios in a single conversation:
Since Dynatrace Assist generates DQL behind the scenes, Cost Intelligence is the optimal way to produce queries you'd otherwise have to write yourself. You can ask Assist to show the query it used, then reuse it in a notebook, dashboard, or workflow.
To use Cost Intelligence, you need the following Dynatrace features and permissions.
davis-copilot:conversations:execute, document:documents:*, and hub:catalog:read.For the full list of permissions and setup steps, see Get started with Dynatrace Intelligence agentic and generative AI.
Keep the following in mind before you start:
Here's how to use Cost Intelligence to learn more about your costs.
Notebooks,
Dashboards, and
Workflows.Here are some example scenarios where you can use Cost Intelligence to get actionable information about your usage and costs.
Treat the prompts below as templates: adjust the capability, timeframe, and grouping to match what you want to investigate.
If you're not sure how to phrase a question, or what needs to be explored further, you can use the following or a similar prompt to ask Dynatrace Assist: What cost drivers can you analyze for me?
This prompt is also a useful conversation starter for teams new to Dynatrace consumption.
Suppose you've received an alert that your Full-Stack Monitoring costs have increased. You want to find the root cause without manually analyzing billing events.
In Dynatrace Assist, enter I received a cost alert that my full-stack costs have increased. Can you check if you find anything notable?
Depending on the response, here are some possible follow-ups:
Break that down by host group.Compare this week's full-stack usage with last week's.Suppose you want to anticipate consumption for an upcoming period based on current trends, for example, before a budget review or when bringing a new team online.
In Dynatrace Assist, enter Based on my log ingest usage over the last 90 days, can you predict my next 30 days?
Depending on the response, here are some possible follow-ups:
Now show me the same forecast for the next 60 and 90 days.What would my log ingest cost be at my contracted rate of <your rate>?Suppose you want to reduce your spending on a capability and need concrete recommendations instead of a simple usage chart.
In Dynatrace Assist, enter Looking at optimizing my log query usage — are there any queries duplicated by multiple users?
Assist will surface overlapping or redundant queries and name the specific queries involved.
Depending on the response, here are some possible follow-ups:
Which queries should I optimize first, and how?Give me a short summary I can share with the team.Dynatrace Assist with Cost Intelligence can supplement your existing tools.
Use: