Metrics powered by Grail overview (DPS)
- Latest Dynatrace
- Overview
- 7-min read
For information about how usage of a specific capability translates to consumption of your DPS license commit, see
Metrics - Ingest & Process feature overview
Here's what's included with the Ingest & Process data-usage dimension:
Concept
Explanation
Data delivery
Delivery of metrics via OneAgent, extensions or ingest API
Topology enrichment
Enrichment of metrics with data source and topology metadata
Data transformation
- Rollup of data to reduced granularity to optimize queries for longer timeframes
- Use of efficient data structures to derive metrics from high volume spans like service response time metrics
Data-retention control
Manage data retention period of incoming metrics based on bucket assignment rules
Metrics - Retain feature overview
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. Metrics retention is defined at the bucket level, ensuring tailored retention periods for specific metrics.
Retention periods
Choose a desired retention period. For the default metrics bucket, the available retention period ranges from 15 months (462 days) to 10 years (3,657 days).
Metrics - Query feature overview
Query usage occurs when:
| Concept | Explanation |
|---|---|
| DQL query execution | A DQL query scans and fetches data that is stored in Grail. |
| App usage | DQL queries can be executed by: - Apps such as  Notebooks,  Dashboards,  Workflows, and  Davis Anomaly Detection.- Dashboard tiles that are based on metrics trigger the execution of DQL queries on refresh - Custom apps - The Dynatrace API |