Events powered by Grail (DPS)
Dynatrace SaaS only
As of April 26, 2023, classic custom events (in other words, custom Davis events, not Business Events powered by Grail) are considered an Early Adopter release on Grail. You will be billed for the ingestion of classic custom events. However, querying classic custom events with DQL, for example via the Notebooks app, does not result in Query consumption.
The unit of measure for consumed events is data volume of ingested events in gibibytes (GiB).
The consumption model for business events is based on three dimensions of data usage (Ingest & Process, Retain, and Query).
Ingest & Process | Retain | Query | |
---|---|---|---|
Definition | Ingested data is the amount of raw data in bytes (logs and events) sent to Dynatrace before enrichment and transformation. | Retained data is the amount of data saved to storage after data parsing, enrichment, transformation, and filtering but before compression. | Queried data is the data read during the execution of a DQL query, including sampled data. |
Unit of measure | per gibibyte (GiB) | per gibibyte-day (GiB-day) | per gibibyte scanned (GiB scanned) |
Ingest & Process
Here's what's included with the Ingest & Process data-usage dimension:
Concept | Explanation |
---|---|
Data delivery | Delivery of business events via OneAgent, RUM JavaScript, or Generic Event Ingestion API (via ActiveGate) |
Topology enrichment | Enrichment of business events with data source and topology metadata |
Data transformation |
|
Data-retention control | Manage data retention periods of incoming business events based on bucket assignment rules |
Conversion to timeseries | Create metrics from business event attributes (note that creating custom metrics generates additional consumption beyond those consumed for ingestion and processing.) |
Apply the following calculation to determine your consumption for the Ingest & Process data-usage dimension:
(number of gibibytes ingested) × (gibibyte price as per your rate card) = consumption in your local currency
Be aware that data enrichment and processing can increase your data volume typically by 0.5-1.0 kB per event. Depending on the source of the data, and the attributes and metadata added during processing, the total data volume after processing can increase by a factor of 2 or more. Processing can also be used to drop unwanted event attributes to reduce retained data volume.
Retain
Here's what's included with the Retain data-usage dimension:
Concept | Explanation |
---|---|
Data availability | Retained data is accessible for analysis and querying until the end of the retention period. |
Retention periods | Choose a retention period
|
Apply the following calculation to determine your consumption for the Retain data-usage dimension:
(number of GiB of processed data ingested per day) × (retention period in days) × (GiB-day price as per your rate card) × (number of days that data is stored) = consumption in your local currency
Query
Query data usage occurs when:
Submitting custom DQL queries in the Logs & Events viewer in advanced mode.
Business Analytics Apps, i.e. Business Flow, Salesforce Insights, Carbon Impact
Executing DQL queries in Notebooks, Workflows, Custom Apps and via API.
Here's what's included with the Query data-usage dimension:
Concept | Explanation |
---|---|
On-read parsing |
|
Aggregation | Perform aggregation, summarization, or statistical analysis of data in events across specific timeframes or time patterns (for example, data occurrences in 30-second or 10-minute intervals), mathematical, or logical functions. |
Reporting | Create reports or summaries with customized fields (columns) by adding, modifying, or dropping existing event attributes. |
Context | Use DQL to analyze event data in context with relevant data on the Dynatrace platform, for example, user sessions or distributed traces. |
Apply the following calculation to determine your consumption for the Query data-usage dimension:
(number of GiB of uncompressed data read during query execution) × (GiB scanned price as per your rate card) = consumption in your local currency
Consumption examples
The following example calculations show how each data-usage dimension contributes to overall usage and consumption.
Step 1 – Ingest & Process
Let's assume that you ingest 5 GiB of business event data per day into Dynatrace. The yearly consumption for Ingest & Process is calculated as follows:
Ingest volume per day | 5 GiB | |
---|---|---|
Ingest volume per year | 1,825 GiB | 5 (GiB per day) × 365 (days) |
Consumption per month in your local currency | 1,825 (GiB per month) × ingest price as per your rate card |
Step 2 – Retain
After processing, enriched data of 9 GiB (5 GiB × 1.8 for enrichment) is added to storage daily and retained for 35 days. The yearly consumption (after a ramp-up period of 35 days) for Retain is calculated as follows:
Retained volume for 1 day | 9 GiB | 5 (GiB data per day) × 1.8 (enrichment) |
---|---|---|
Retained volume for 35 days | 315 GiB | 9 (GiB per day) × 35 (days) |
Consumption per day in your local currency | 315 (GiB) × retain price per day as per your rate card | |
Consumption per year in your local currency | 315 (GiB) × retain price per day as per your rate card × 365 (days) |
If the same amount of processed data is added to storage daily and retained for 365 days, the monthly consumption (after a ramp-up of 365 days in this case) for Retain is calculated as follows:
Retained volume for 1 day | 9 GiB | 500 (GiB data per day) × 1.8 (enrichment) |
---|---|---|
Retained volume for 365 days | 3,285 GiB | 900 (GiB per day) × 35 (days) |
Consumption per day in your local currency | 3,285 (GiB) × retain price per day as per your rate card | |
Consumption per year in your local currency | 3,285 (GiB) × retain price per day as per your rate card × 30 (days) |
Step 3 – Query
Let's assume that to resolve incidents and analyze performance issues your team executes DQL queries with a total of 250 GiB of data read per day. The monthly consumption for Query is calculated as follows:
Data volume read per day | 250 GiB | |
---|---|---|
Data volume read per year | 91,250 GiB | 250 (GiB per day) × 365 (days) |
Consumption per year in your local currency | 91,250 (GiB per year) × query price as per rate card |
Step 4 – Total consumption
The total annual consumption for this example scenario of 35 days of data retention is the sum of the yearly consumption for Ingest & Process, Retain, and Query.
Consumption details
Dynatrace provides built-in metrics that help you understand and analyze your organization's consumption of Ingest & Processing, Retain and Query for Events powered by Grail. To use them in Data Explorer, enter Business events into the Search field. These metrics are also available via the Environment API and linked in Account Management (Usage summary > Events – Ingest & Process, Retain, Query > Actions > View details). The table below shows the list of metrics you can use to monitor the consumption details for Events powered by Grail.
- Business events usage - Ingest & Process
Key:
builtin:billing.events.business_events.ingest.usage
Dimension: Byte
Resolution: 1 hour
Description: Number of raw bytes sent to Dynatrace before enrichment and transformation in hourly intervals.
- Business events usage - Retain
Key:
builtin:billing.events.business_events.retain.usage
Dimension: Byte
Resolution: 1 hour
Description: Number of bytes saved to storage after data parsing, enrichment, transformation, and filtering but before compression.
- Business events usage - Query
Key:
builtin:billing.events.business_events.query.usage
Dimension: Byte
Resolution: 1 hour
Description: Number of bytes read during the execution of a DQL query, including sampled data.
Ingest & Process
You can monitor the total bytes ingested for Ingest & Processing in hourly intervals for any selected timeframe by using the Business events usage - Ingest & Process metric. The example below shows the usage aggregated in 1-hour intervals between 2023-09-04 and 2023-09-11 (Last 7 days).
Retain
You can monitor the total usage in bytes stored for Retain in hourly intervals for any selected timeframe by using the Business events usage - Retain metric. The example below shows the usage aggregated in 1-hour intervals between 2023-09-04 and 2023-09-11 (Last 7 days).
Query
You can monitor the total scanned bytes for Query in hourly intervals for any selected timeframe using the metric Business events usage - Query. The example below shows usage aggregated in 1-hour intervals between 2023-09-04 and 2023-09-11 (Last 7 days).