Summary
- The public price page bills in eight different units of account: memory-GiB-hour for host monitoring, GiB for log, trace and event ingest, GiB-day for retention, GiB-scanned for queries, 100,000 datapoints for metrics, 1,000 sessions, 1,000 synthetic actions and 1,000 synthetic requests. It defines none of them.
- The three readable capability pages that do define a meter define three different dimensions: memory multiplied by hours, raw bytes counted before enrichment, and sessions plus session properties counted per application and per starting hour.
- My division of the printed $58 card by the printed $0.01 per memory-GiB-hour rate gives 725 hours, which is none of 720, 730 or 744; the price page carried no effective date, and the document that would carry the older unit weights returned no readable text.
Dynatrace publishes a rate for eight different things and a definition for none of them on the page that charges you. The definitions live elsewhere, and when you find them they measure three different quantities: memory multiplied by time, raw bytes counted before the vendor touches them, and events counted by a rule your own architecture decides.
The first number on the price page looks like a price and is a rate in a coat. Full-Stack Monitoring is displayed as $58 / mo per 8 GiB host. The footnote beneath it reads: billed at $0.01 per memory-GiB-hour.
Divide one by the other and the month the card was written for falls out. $58 ÷ (8 GiB × $0.01) = 725 hours. A 730-hour month of one 8 GiB host is $58.40; a 720-hour month is $57.60; a 744-hour month is $59.52. The printed card matches none of the three. That division is mine, not the vendor's. The page prints an hourly rate and a monthly restatement of it and leaves the hours in between to whoever wants them.
Eight things you can be charged for
Scan the public price list and count the denominators, not the products. A memory-GiB-hour for host monitoring. A plain GiB for log, trace and event ingest. A GiB-day for retention. A GiB-scanned for queries. A block of 100,000 datapoints for metrics. A thousand sessions for real user monitoring. A thousand synthetic actions for browser monitors and clickpaths. A thousand synthetic requests for HTTP monitors.
Eight different units of account on one page, priced at $0.01 per memory-GiB-hour, $0.20 per GiB ingested, $0.0007 per GiB-day retained, $0.0035 per GiB-scanned, $0.02 per GiB-day for retention with queries included, $0.15 per 100,000 datapoints, $2.25 per thousand sessions, $4.50 per thousand sessions with replay capture, $4.50 per thousand synthetic actions and $1.00 per thousand synthetic requests.
Four of those denominators share the letters GiB and are not the same object. Ingest is a volume at the door. Retain is a volume held for a day. Scanned is a volume read for a query. Metrics escape the family entirely, because a datapoint is counted rather than measured in bytes. Sessions and synthetic actions are counted events, and the price page counts them per thousand.
Now look for a sentence on that page that says what any of them includes, excludes, rounds or floors. There is none. The page is a list of rates over a list of nouns.
What the definitions actually say
The nouns are defined, and the defining sentences are short enough to quote whole. On the Full-Stack Monitoring consumption page: "Dynatrace uses GiB-hours (referred to as "memory-gibibyte-hours" in your rate card) as the unit of measure for calculating your organization's consumption of host monitoring in Full-Stack Monitoring mode." On the log analytics page: "Ingested data is the amount of raw data in bytes sent to Dynatrace before enrichment and transformation.
It is calculated per gibibyte (GiB)." On the real user monitoring page: "The unit of measurement for RUM consumption is sessions, plus the number of session properties that are captured within those sessions."
Three sentences, three dimensions. The first is memory times hours. The second is bytes before the platform does anything to them, which is a deliberate choice of perimeter: you are billed on what you sent, not on what the pipeline made of it. The third is a counted object with an internal multiplier, because a session is not one thing. A single visit that touches three instrumented applications counts as three sessions, one per application, and a visit that stays longer than an hour in one application starts another session for each additional starting hour. Sessions with only one user action are bounced and do not count at all.
That last cluster of rules is the part of the price list the buyer writes. Nothing in the vendor's documents can tell you how many sessions your site produces, because the count is a function of how your front end is instrumented and how your visitors move. One visit across three applications is $0.00675 at the printed $2.25 per thousand, and that figure is my multiplication of a printed rate by a printed counting rule, not the vendor's estimate of your bill.
Where the meter's zero sits
The floors are printed, and they are the most consequential numbers in the corpus. Host RAM is rounded up to the next 0.25 GiB before anything is calculated, so a host reporting 8.1 GiB is metered at 8.25 GiB, about 1.85 percent above its own memory by my division. A 4 GiB minimum applies to physical and virtual hosts, and the page's own example counts a 2 GiB host as a 4 GiB host, which at $0.01 per memory-GiB-hour bills $0.04 an hour for a machine holding $0.02 worth by its own stated capacity.
Application-only container monitoring uses a 256 MiB minimum instead, one sixteenth of the host floor by my arithmetic on the two printed figures, because 4,096 ÷ 256 = 16.
Time is floored too. Consumption is calculated in 15-minute intervals, and a host monitored for less than 15 minutes inside an interval is rounded up to 15 minutes, so one minute of monitoring in an interval is billed as fifteen by the rate the page prints.
None of those rules is on the price page. A reader who wants to know what a memory-GiB-hour costs can stop at one address. A reader who wants to know what their own estate will cost has to hold a second address, and the second address does not mention the first.
The retention arithmetic nobody prints
Retention is priced per GiB-day, which makes two comparisons available from printed figures alone. Both are mine. At $0.0007 per GiB-day, keeping one GiB for a year costs $0.2555, which is 1.28 times the $0.20 it cost to ingest it once. On this price list, storage is the larger line item for anything kept more than about 286 days, which is the day count at which $0.20 ÷ $0.0007 is reached.
The second comparison is the bundle. Retain with included queries is priced at $0.02 per GiB-day against a base retain rate of $0.0007, a factor of 28.571. The bundle pays for itself when a retained GiB is scanned more than 5.51 times a day, which is my division of the $0.0193 difference by the $0.0035 per-GiB scan rate. For a small log estate queried hard, the bundled rate wins; for a large one queried occasionally, it does not. And because re-scanning the same GiB 57 times costs about what writing it once costs at $0.20 ÷ $0.0035, the scan regime matters more than most buyers assume when they choose a retention tier.
What the six addresses do not say
This piece read six addresses on 21 November 2026, and the boundaries of what they establish belong beside the numbers.
The pricing page prints no definition of any unit it prices and no effective date for the list. The text returned was apparently truncated before the end of the page. The Full-Stack Monitoring consumption page, the log ingest page and the real user monitoring page each define their own meter and none of them names another meter. The licensing overview, dated 4 May 2026, describes the commercial shape: an agreement typically of one to three years with a minimum annual commitment, usage accruing against that commitment at rate-card unit prices, and on-demand consumption beyond it without overage premiums. It states no conversion between this platform subscription's meters and any earlier licensing unit, and it does not say which instrument governs an existing customer's renewal.
That is the stop, and it should be named precisely rather than smoothed over. The document that would carry the older unit weights is the Platform Usage Supplement dated 21 March 2025 in its own filename, and on retrieval it returned no readable text. Nothing in this article is taken from its contents. Four addresses under the classic-licensing path also returned HTTP 404 on the same date, and no claim is made about what they hold. The glossary returned readable text that stopped before the host-unit entries, so nothing is quoted from it either.
Six addresses, then, and three of them define a meter. Where the arithmetic has to stop is exactly where the definitions stop: at the notional unit, which this corpus cannot convert, and at the month, which the price page prints as a card without printing the hours inside it.
What the page is
Dynatrace does not publish a price list. It publishes rates in eight units of account on one page, and it publishes the definition of three of those units on three other pages, each written for the capability it describes. The joins between them are left to the buyer, and two of the joins cannot be made from the documents at all: the month behind the $58 card, and the counted events that only your own instrumentation can enumerate.
There is nothing hidden about this. Every number in this article is printed on a public page, and the floors, intervals and counting rules are printed in sentences short enough to quote. The finding is documentary rather than accusatory: the vendor has told the truth in eight dimensions, and a reader who wants one number has to assemble it from three addresses and supply the multiplier themselves. That is not a price. It is a specification with rates attached.
Dynatrace LLC is tracked in the BTW directory: Dynatrace LLC.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






