QUOTATRACE01
Runs entirely in your environment.
Analysis and report generation run on your machine. No QuotaTrace cloud is required.
QuotaTrace · License analysis for Dynatrace Managed
Which systems consume your Dynatrace license?
QuotaTrace analyzes billing data from your Dynatrace Managed environment locally and shows which environments, hosts and Kubernetes namespaces consume host units, DEM units and DDU.
Illustration with example data.
What the License Assessment shows.
One settled period, broken down by environment, host and pool. HU and DEM are estimates; DDU are taken from the billing data.
The starting point
Three questions for your billing data.
- 01
Which environments consume the most host units?
QuotaTrace totals host units per environment and ranks them by consumption.
- 02
Which hosts consume the most?
You can sort, filter and compare hosts by host units.
- 03
How are DDU split across pools?
Reported DDU are shown per pool, such as Metrics, Log Monitoring or Custom Traces, with the largest contributors.
From total to consumer
From billing archive to per-host results.
The Assessment imports local archives or reads a settled period directly from Dynatrace Managed.
-
Billing archive
Import a JSON or ZIP export.
-
HU / DEM / DDU
Calculate HU and DEM, use reported DDU as-is.
-
Environment
Compare consumption by environment.
-
Hosts & namespaces
Inspect individual hosts and Kubernetes namespaces.
Technical context
What gets analyzed.
The Assessment covers everything from import to report.
Billing import
JSON exports and nested ZIP archives for one settled period.
HU / DEM
Calculated units with documented assumptions and warnings for missing data.
DDU
Reported DDU per pool with the largest contributors.
Environments & hosts
Filter, search and compare, including host groups and Kubernetes namespaces.
Local results
PDF report and portable assessment file.
Managed connection
Collection over HTTPS directly from your Managed cluster.
The result
A report with sources, assumptions and data gaps.
The Assessment ranks the areas with the largest effect on your license consumption. You save the results as a PDF and as a portable file.
-
Period
Settled billing data
-
Attribution
Environments, hosts and namespaces
-
Prioritization
Review areas ranked by impact
Offerings
One-off analysis or ongoing monitoring.
The License Assessment analyzes one settled period. Continuous Optimization tracks consumption on an ongoing basis and exposes it as metrics.
One settled period
License consumption per environment and host.
The Assessment runs as a Windows application or CLI in your environment. The result is a PDF report you can share internally.
- Local import or Managed collection
- Host units, DEM units and DDU per environment and host
- Host groups and Kubernetes namespaces
- Prioritized review areas with assumptions and warnings
- PDF report and portable assessment file
We agree on scope, access and support with you in a first call.
Process
- Import Archive or Managed API 01
- Calculate HU, DEM and DDU from billing data 02
- Analyze Attribution and prioritization 03
- Report PDF and portable file 04
Always-on service
License consumption as metrics in Dynatrace.
A service for Windows, Linux or OpenShift collects consumption at regular intervals and exposes it as license metrics for Dynatrace and optionally for Prometheus/Grafana.
- Regular data collection
- Trends and period comparisons
- Dynatrace metrics and dashboards
The illustration shows a dashboard with example data.
Integration
The service runs in your infrastructure and reads the same cluster APIs as the Assessment.
- 01
Deployment
As a Windows or Linux service, or as a workload on OpenShift.
- 02
Access
Reads license and consumption data from the Dynatrace Managed cluster APIs.
- 03
Analysis
Metrics in Prometheus format for Dynatrace dashboards and optionally for Prometheus/Grafana. Metrics ingested by Dynatrace consume DDU from the metrics pool themselves.
Technical facts
- Platforms
- Windows / Linux / OpenShift
- Format
- Prometheus
- Outputs
- Dynatrace, optional Prometheus/Grafana
Data flow
- Dynatrace Managed Cluster and environment APIs
- QuotaTrace Continuous Service in your infrastructure
- License Metrics Prometheus format
- Dynatrace Dashboard Native analysis
Technical architecture
How QuotaTrace works.
Windows application and CLI
Both calculate the same way and produce the same results.
Managed APIs
Collection reads cluster license and consumption data over HTTPS.
Enterprise networks
Custom CA certificates and proxy configuration are supported.
Sources and assumptions
Reports include the analyzed period, assumptions and coverage warnings.
About the calculation
QuotaTrace derives host units from each host's memory and monitoring mode, following Dynatrace's host unit table. HU and DEM units are estimates based on documented assumptions. DDU are taken as reported by Dynatrace. Missing data is not counted as zero consumption.
Local
Your Dynatrace data stays in your environment.
The Assessment processes billing data and generates reports locally. No data is sent to Convexio or any third party.
02
Connects only to your cluster.
During collection, the Assessment connects only to the Managed cluster you select. Imported archives are processed locally.
03
No product telemetry.
QuotaTrace contains no usage analytics and no tracking.
04
Read-only access.
The Assessment reads the cluster's license and consumption endpoints using GET and does not change any Dynatrace configuration.
-
Session tokens
Tokens stay in memory for the session only and are not saved in assessment files.
-
No secrets in CLI arguments
The CLI client reads tokens from environment variables.
-
Results contain internal data
PDFs and saved assessments can contain hostnames, identifiers and usage. They are not encrypted.
Analyses
Where license consumption can be reduced.
QuotaTrace attributes consumption and ranks the areas your team should review first.
Review monitoring mode
Finds hosts running Full Stack where Infrastructure Monitoring might be enough.
Spot unusual consumers
Shows hosts and workloads whose consumption is unusually high for their role.
Consumption by Kubernetes namespace
Attributes node consumption to individual Kubernetes clusters and namespaces.
DDU hotspots
Shows large or unexpected data sources per DDU pool, including shares that cannot be attributed to a contributor.
Plan license needs
The actual distribution and how it changes across periods serve as a basis for capacity and license decisions.
QuotaTrace shows where units are consumed. Which changes you make is up to your Dynatrace team.
Host units in detail
Host units per host, with the reasoning behind them.
For every host, QuotaTrace shows host units alongside monitoring mode, memory, host group and Kubernetes mapping. If input data is missing, QuotaTrace marks the value as unknown.
Illustration with example data. HU are estimates based on memory and monitoring mode.
Business case
What one percent of your Dynatrace budget is worth.
With large Dynatrace contracts, even a small share of avoidable consumption can add up to six figures a year. Calculate with your own assumptions.
€
License cost per year, in euros
5%
Calculated savings
€100,000 / year
€2,000,000 × 5%
Comparison scenarios
Illustrative example. No guarantee of savings. The actual economic impact depends in particular on licensing model, contract, usage and technical environment.
Is QuotaTrace a fit for your Dynatrace environment?
We'll talk about your environment, your questions about license consumption and which offering fits.