DDUs for Logs and Events on Grail
This page explains the concept of Logs and Events on Grail, how we calculate DDUs for Logs and Events on Grail, and how you can estimate and track DDU consumption if you use Logs and Events on Grail. The new pricing model outlined below will only affect customer accounts and tenants after being activated for and connected to a Grail cluster for logs data.
What are Logs and Events on Grail?
Logs and Events powered by Grail is a solution integrated into the Dynatrace Software Intelligence Platform. You can gain direct access to the log content of all your mission-critical processes. The setup and configuration is easy with no indexing required. Logs and Events powered by Grail provide scaling options, flexible data retention periods, and a solid analytics toolkit based on the Dynatrace Query Language (DQL). Finally, the solution offers a new, volume-based pricing model.
Creating metrics, which consumes DDUs according to custom metrics calculation, enables you to interpret and analyze your log data, as well as understand user impact.
How is DDU consumption calculated?
Apart from the DDU-based calculation, Log, and Events powered by Grail also consider the volume of data used, measured in gigabytes (GB). For example, searching through 1 TB of retained data during a DQL-query execution consumes 1,850 DDUs.
This model replaces the current approach of charging per log event used in Log Monitoring. It makes it possible to manage your logs and events at scale, particularly in cloud environments.
There are three pillars of billing. You can choose one, two or three (or any combination) of the pillars listed below:
- Ingest and process
Usage measured per gigabyte of data ingested and processed - Retain
Usage measured per gigabyte of data stored per day - Query
Usage measured per gigabyte of data searched through within the Grail database
Ingest and process
The data volume delivered via OneAgent or the Generic Log Ingestion APIs, is measured in gigabytes (GB). Every ingested and processed GB of data deducts 100 DDUs from your available quota.
To calculate your DDU consumption, multiply the total number of gigabytes ingested by the DDU weight, and by the time period measured in days.
For example, if the total amount of log data sent to Dynatrace was 60 GB per day:
- The monthly DDU consumption for Ingest & Process is 180,000 DDUs (60 GB log data x 100 DDUs x 30 days)
- The annual DDU consumption is 2,190,000 DDUs (60 GB x 100 DDUs x 365 days)
Retain
With Log and Events powered by Grail you can implement your data retention strategy depending on your business needs. Your data can be accessed at any time for ad-hoc DQL queries. Dynatrace determines your usage by measuring the daily gigabytes (GB) stored on Grail. For every gigabyte of data stored on Grail, 0.30 DDUs gets deducted from your quota.
For example, if you add 1,250 GB of data on a daily basis and decide to keep it for 35 days:
- The monthly DDU consumption is 393,750 DDUs (1,250 GB x 35 retention days x 0.30 DDUs per day x 30 days)
- The annual DDU consumption is 4,790,625 DDUs (1,250 GB x 35 retention days x 0.30 DDUs per day x 365 days).
In case you decide to store the data for a year:
- The monthly DDU consumption is 4,106,250 DDUs (1,250 GB x 365 retention days x 0.30 DDUs per day x 30 days)
- The annual DDU consumption is 49,959,375 DDUs per year (1,250 GB x 365 retention days x 0.30 DDUs per day x 365 days).
Query
Queries written in the Dynatrace Query Language (DQL) allow you to explore and analyze your data. Dynatrace determines your usage by measuring how many gigabytes of data were searched within the Grail database during the query execution. For every gigabyte of data searched using the DQL query, 1.70 DDUs gets deducted from your quota.
For example, if you execute DQL queries that search through an average of 12 TB of data stored in Grail per day:
- The monthly DDU consumption is 612,000 DDUs (12,000 GB x 1.70 DDUs x 30 days),
- The annual DDU consumption is 7,446,000 DDUs (12,000 GB x 1.70 DDUs x 365 days).
Calculation summary table
Pillar name | Pillar definition | DDU weight | DDU daily usage calculation |
---|---|---|---|
Ingest and process | Amount of data sent to Dynatrace via OneAgent and/or API before processing takes place. | 100 per GB |
|
Retain | Amount of data sent to storage after data processing and before data compressing. | 0.30 per GB per day |
|
Query | Amount of data searched during the execution of a DQL query. Includes sampled data. | 1.70 per GB of data searched |
|