Skip to content

Know where your Dynatrace consumption comes from.

QuotaTrace makes your Dynatrace license consumption transparent down to the host and shows concrete optimization potential – for Managed and SaaS.

Illustrative Assessment view with example data

How the License Assessment makes your consumption transparent.

The starting point

Three questions for your billing data.

  1. 01

    Which environments consume the most?

  2. 02

    Which hosts consume the most?

  3. 03

    How are DDU split across pools?

From total to consumer

From billing data to per-host results.

  1. Billing data

    Import an archive or read directly from Dynatrace.

  2. HU or DPS

    Determine host units or DPS consumption, depending on the license model.

  3. Environment

    Compare consumption by environment.

  4. Hosts & namespaces

    Inspect individual hosts and Kubernetes namespaces.

Technical context

What gets analyzed.

  • Billing import

    JSON exports and nested ZIP archives for one settled period.

  • Host units & DPS

    The classic host unit model and consumption-based billing through Dynatrace Platform Subscription (DPS), mainly GiB-hours and host-hours.

  • 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 & SaaS

    Collection over HTTPS directly from your Managed cluster or SaaS environment.

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.

  1. Period

    Settled billing data

  2. Attribution

    Environments, hosts and namespaces

  3. Prioritization

    Review areas ranked by impact

Treemap

All consumption at a glance.

Treemap view in QuotaTrace: host units grouped by Kubernetes cluster

Offerings

One-off analysis or ongoing monitoring.

Two ways to make your Dynatrace license consumption transparent.

License Assessment

Identify consumption drivers.

A one-off analysis of your billing data from Dynatrace Managed or SaaS with a structured results report.

  • Host units or DPS consumption by environment and host
  • Host groups and Kubernetes namespaces in detail
  • Prioritized review areas with assumptions and warnings
Request an Assessment

The Assessment runs as a Windows application or CLI in your environment and analyzes one settled period.

Billing import
JSON exports and nested ZIP archives for one settled period.
Host units or DPS
Host units with documented assumptions, or billed GiB-hours and host-hours from DPS.
DDU
Reported DDU per pool with the largest contributors.
Environments & hosts
Filter, search and compare, including host groups and Kubernetes namespaces.
Runs as
Windows application / CLI
Data source
Billing archive, Managed or SaaS
Result
PDF report and assessment file
  1. Import
  2. Calculation
  3. Analysis
  4. Report

Continuous Optimization

Steer license consumption.

QuotaTrace collects consumption on an ongoing basis and provides it as license metrics.

  • Continuous collection from Dynatrace Managed or SaaS
  • Trends and period comparisons
  • License metrics and dashboards right inside Dynatrace
Request Continuous

The service runs in your infrastructure and reads the same Dynatrace APIs as the Assessment.

Deployment
As a Windows or Linux service, or as a workload on OpenShift.
Access
Reads license and consumption data from Dynatrace Managed or SaaS.
Analysis
Metrics in Prometheus format for Dynatrace dashboards and optionally for Prometheus/Grafana.
Note
Metrics ingested by Dynatrace count toward license consumption themselves.
Platforms
Windows / Linux / OpenShift
Format
Prometheus
Outputs
Dynatrace, optional Prometheus/Grafana
  1. Dynatrace
  2. QuotaTrace
  3. Metrics
  4. Dashboard

Technical architecture

How QuotaTrace works.

Windows application and CLI

Both calculate the same way and produce the same results.

Dynatrace APIs

Collection reads license and consumption data from Managed or SaaS 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

With classic licensing, 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. With DPS, QuotaTrace uses the billed GiB-hours and host-hours. It calculates monetary savings there only with the prices from your rate card. 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.

01

Runs entirely in your environment.

Analysis and report generation run on your machine. No QuotaTrace cloud is required.

02

Connects only to Dynatrace.

During collection, the Assessment connects only to the Managed cluster or SaaS environment you select. Convexio receives no usage or monitoring data.

03

No product telemetry.

QuotaTrace contains no usage analytics and no tracking.

04

Read-only access.

The Assessment reads license and consumption data and does not change any Dynatrace configuration.

  • No tokens in files

    Tokens are not saved in assessment files. Remembered connections are kept in the operating system's credential store.

  • 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 consumption comes from. Which changes you make is up to your Dynatrace team.

Host level

License consumption down to the host.

Depending on the license model in host units or, with DPS, in GiB-hours and host-hours. The view shows an example with host units.

Hosts view in QuotaTrace: hosts grouped by host group, with environment, Kubernetes cluster, monitoring mode, memory and estimated host units

Find out what's inside your Dynatrace environment.

We show where consumption comes from, where optimization pays off and which QuotaTrace approach fits.