Dynatrace Pricing Explained: How the Rate Card and Commitment Work

By Sazabi Team

Prices checked on vendor pages on Nov 8, 2026.

Dynatrace does not sell plans by tier. It sells a Dynatrace Platform Subscription (DPS): you commit to a minimum annual spend, and every capability draws that commitment down at a published rate card. This guide uses the list prices on the pricing page as of November 8, 2026.

Two things shape a real quote. Your commit size sets your discount, and the page shows list rates before any discount. Treat the numbers below as the ceiling, not a quote.

The Short Version

  • Full-Stack Monitoring is $58 per month for an 8 GiB host, billed at $0.01 per memory-GiB-hour.
  • Logs ingest at $0.20 per GiB, then you choose how retention and queries are billed.
  • Overages are never penalties. Extra use is billed on demand at the same rate.
  • Seats are unlimited, so users do not add cost.
  • A larger commitment lowers your unit price.

How The Subscription Works

Dynatrace's docs say a DPS agreement has a minimum commitment of one year, and agreements usually run one to three years. Usage accrues against your annual commit as the rate card prices it.

If you pass the commit, nothing breaks. You continue on demand, billed monthly at the same rates, with no premium. Or you can raise the commit for a bigger discount. Metering runs on UTC, and fractions of an hour round up to the nearest 15 minutes, so one minute of use bills as 15.

Host And Container Prices

CapabilityList PriceBilling Basis
Foundation and Discovery$7 per month$0.01 per host-hour
Infrastructure Monitoring$29 per month$0.04 per host-hour
Full-Stack Monitoring$58 per month per 8 GiB host$0.01 per memory-GiB-hour
Kubernetes Platform Monitoring$1.40 per month per pod$0.002 per pod-hour
Code Monitoring$3.60 per month per container$0.005 per container-hour

Full-Stack pricing follows memory, not host count. A 64 GiB host is eight 8 GiB units, so about $464 per month at list. Kubernetes Platform Monitoring is included on hosts with Full-Stack Monitoring.

How Dynatrace Charges For Logs

Log Analytics has two billing models, and you can mix them across your environment.

ModelIngest and ProcessRetainQuery
Pay-per-Query$0.20 per GiB$0.0007 per GiB-day$0.0035 per GiB scanned
Bundled Queries$0.20 per GiB$0.02 per GiB-day, queries includedIncluded

Pay-per-Query allows retention from 1 day to 10 years. Bundled Queries covers a minimum of 10 and up to 35 days of retention, extendable with the usage-based option. A GiB is about 7% larger than a GB. The comparison below treats them as equal.

Other data types follow the same shape. Traces and events are $0.20 per GiB ingested, $0.0007 per GiB-day retained, and $0.0035 per GiB scanned. Metrics are $0.15 per 100,000 data points ingested with queries at no additional cost.

Other Meters On The Page

  • Real User Monitoring: $2.25 per 1,000 sessions, or $4.50 per 1,000 with session replay capture.
  • Browser Monitor: $4.50 per 1,000 synthetic actions. HTTP Monitor: $1.00 per 1,000 requests.
  • Runtime Vulnerability Analytics and Runtime Application Protection: $13 per month per 8 GiB host each.
  • Security Posture Management: $5 per month per host.
  • Agentic Operations: $0.10 per AI unit.

AI Exploration is listed as included at no additional charge. Agentic Operations tasks draw AI units, and the page gives averages: 2 units to translate DQL into plain language, 8 units for the reverse, and 30 units for an autonomous multi-step investigation. At $0.10 per unit, that last one averages about $3.00 per run. The page says those tasks are not billed inside Dynatrace Assist for a limited time, but are billed through workflows, MCP, the API, or custom apps.

A Worked Month At List Price

Assumptions: 10 Full-Stack hosts of 8 GiB each, 10 Infrastructure Monitoring hosts, and 500 GiB of logs a month on Pay-per-Query. Logs are kept 30 days, so about 500 GiB sits in storage, and queries scan 40% of ingested volume (our assumption). We leave out metrics, traces, RUM, security, and AI units, and we apply no commit discount.

Line ItemMathCost
Full-Stack hosts10 x $58$580.00
Infrastructure hosts10 x $29$290.00
Log ingest500 GiB x $0.20$100.00
Log retention500 GiB x 30 days x $0.0007$10.50
Log queries200 GiB x $0.0035$0.70
Total$981.20

Hosts are about 89% of that bill. Logs are cheap in this model. On Bundled Queries the same logs would cost $100 to ingest plus $300 to retain (500 GiB x 30 days x $0.02), or $400, which is a real difference to model before you sign.

Controls And Visibility

The docs describe a DPS account with three default budget alerts, at 75%, 90%, and 100% of the annual commitment. You can add budgets by environment or capability, such as a threshold on a new capability. Budgets are evaluated daily, after the cost run that usually finishes by 12

UTC. In Account Management, under Subscription, you get a budget summary, a 30-day breakdown, and a drilldown analysis. Budget alerts are not available on trials or proofs of concept.

Where Sazabi Compares

Sazabi is AI-native observability and security, and it covers logs, not Dynatrace's host, RUM, and security catalog. This comparison is logs only, and we are a party to it.

Sazabi's Startup plan is $200 per 30-day cycle and includes 200 GB ingested and 50 GB scanned, then $0.10 per GB for each. Retention is 30 days.

Monthly LogsDynatrace Pay-per-QueryDynatrace Bundled QueriesSazabi Startup
100 GB$22.24$80$200
1,000 GB$222.40$800$315
10,000 GB$2,224.00$8,000$1,575

Assumptions: list rates with no commit discount, 30-day retention, and scans at 40% of ingest on both sides. Sazabi leaves out issues past the included 20 and AI credits past 500. Dynatrace Pay-per-Query is cheaper through 1,000 GB at list, and Sazabi is cheaper at 10,000 GB. Dynatrace logs also require a DPS commitment, and Sazabi has no yearly billing.

Where Sazabi differs is the workflow. It detects issues from logs without hand-built monitors, investigates root cause, and hands it to your coding agent through MCP, CLI, or API. If you collect with an OpenTelemetry Collector, you can add Sazabi as one more exporter and try it next to Dynatrace. See Sazabi pricing and the Sazabi vs Dynatrace comparison. Our OpenTelemetry integration page covers the setup options.

When Dynatrace Is Worth The Price

Dynatrace fits large estates where host and process topology detection, APM, Kubernetes, RUM, synthetics, and application security under one contract matter more than a lean logs bill. Unlimited seats help when many teams need access. If one commitment across all of that appeals to procurement, the model is simple. If you only need logs, read the Dynatrace alternatives guide before committing.

Frequently Asked Questions

How does Dynatrace charge for logs?

On the pricing page, Log Analytics offers two models. Pay-per-Query is $0.20 per GiB ingested, $0.0007 per GiB-day retained and $0.0035 per GiB scanned. Bundled Queries is $0.20 per GiB ingested and $0.02 per GiB-day retained with queries included.

Does Dynatrace charge overage penalties?

No. Dynatrace says it never charges penalty-style overages. If you use more than your annual commitment, you keep using the platform on demand at the same rates, billed monthly.

Is there a per-user fee in Dynatrace?

The pricing page lists unlimited seats, with no per-seat fees or user tiers. Cost comes from the capabilities you consume, such as hosts, ingested GiB and AI units.

Can I run Dynatrace and Sazabi side by side?

If you collect telemetry with an OpenTelemetry Collector, Sazabi can be added as another OTLP/HTTP exporter next to your existing ones. Both destinations then receive the same logs and traces.

Sources

  1. List prices and billing units for host monitoring, Log Analytics, metrics, traces, events, AI units, RUM, synthetics and security; DPS commitment model (accessed Nov 8, 2026)
  2. No penalty-style overages, on-demand billing at the same rates, 15-minute billing rounding, UTC metering (accessed Nov 8, 2026)
  3. Default budget thresholds at 75%, 90% and 100% of the annual commitment; configurable budgets by environment and capability (accessed Nov 8, 2026)
  4. Where to see consumption in Account Management, minimum one-year term, on-demand usage after the commitment is reached (accessed Nov 8, 2026)
  5. Sazabi plan prices, included allowances, per-GB overage rates and retention (accessed Nov 8, 2026)
  6. Adding Sazabi as an additional OTLP/HTTP exporter in an OpenTelemetry Collector alongside existing exporters (accessed Nov 8, 2026)