Built-in metrics

Reported error count (by OS, app version) [custom]

The number of all reported errors.

Session count (by OS, app version) [custom]

The number of captured user sessions.

Session count (by OS, app version, crash replay feature status) [mobile]

The number of captured user sessions.

Session count (by OS, app version, full replay feature status) [mobile]

The number of captured user sessions.

Reported error count (by OS, app version) [mobile]

The number of all reported errors.

User action rate - affected by JavaScript errors (by key user action, user type) [web]

The percentage of key user actions with detected JavaScript errors.

Apdex (by key user action) [web]

The average Apdex rating for key user actions.

Action count - custom action (by key user action, browser) [web]

The number of custom actions that are marked as key user actions.

Action count - load action (by key user action, browser) [web]

The number of load actions that are marked as key user actions.

Action count - XHR action (by key user action, browser) [web]

The number of XHR actions that are marked as key user actions.

Cumulative Layout Shift - load action (by key user action, user type) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions that are marked as key user actions.

Cumulative Layout Shift - load action (by key user action, geolocation, user type) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions that are marked as key user actions.

Cumulative Layout Shift - load action (by key user action, browser) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions that are marked as key user actions.

DOM interactive - load action (by key user action, browser) [web]

The time taken until a page's status is set to "interactive" and it's ready to receive user input. Calculated for load actions that are marked as key user actions.

Action duration - custom action (by key user action, browser) [web]

The duration of custom actions.

Action duration - load action (by key user action, browser) [web]

The duration of load actions that are marked as key user actions.

Action duration - XHR action (by key user action, browser) [web]

The duration of XHR actions that are marked as key user actions.

Time to first byte - load action (by key user action, browser) [web]

The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Calculated for load actions that are marked as key user actions.

Time to first byte - XHR action (by key user action, browser) [web]

The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Calculated for XHR actions that are marked as key user actions.

First Input Delay - load action (by key user action, user type) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions that are marked as key user actions.

First Input Delay - load action (by key user action, geolocation, user type) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions that are marked as key user actions.

First Input Delay - load action (by key user action, browser) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions that are marked as key user actions.

Largest Contentful Paint - load action (by key user action, user type) [web]

The time taken to render the largest element in the viewport. Calculated for load actions that are marked as key user actions.

Largest Contentful Paint - load action (by key user action, geolocation, user type) [web]

The time taken to render the largest element in the viewport. Calculated for load actions that are marked as key user actions.

Largest Contentful Paint - load action (by key user action, browser) [web]

The time taken to render the largest element in the viewport. Calculated for load actions that are marked as key user actions.

Load event end - load action (by key user action, browser) [web]

The time taken to complete the load event of a page. Calculated for load actions that are marked as key user actions.

Load event start - load action (by key user action, browser) [web]

The time taken to begin the load event of a page. Calculated for load actions that are marked as key user actions.

Network contribution - load action (by key user action, user type) [web]

The time taken to request and receive resources (including DNS lookup, redirect, and TCP connect time). Calculated for load actions that are marked as key user actions.

Network contribution - XHR action (by key user action, user type) [web]

The time taken to request and receive resources (including DNS lookup, redirect, and TCP connect time). Calculated for XHR actions that are marked as key user actions.

Response end - load action (by key user action, browser) [web]

(AKA HTML downloaded) The time taken until the user agent receives the last byte of the response or the transport connection is closed, whichever comes first. Calculated for load actions that are marked as key user actions.

Response end - XHR action (by key user action, browser) [web]

The time taken until the user agent receives the last byte of the response or the transport connection is closed, whichever comes first. Calculated for XHR actions that are marked as key user actions.

Server contribution - load action (by key user action, user type) [web]

The time spent on server-side processing for a page. Calculated for load actions that are marked as key user actions.

Server contribution - XHR action (by key user action, user type) [web]

The time spent on server-side processing for a page. Calculated for XHR actions that are marked as key user actions.

Speed index - load action (by key user action, browser) [web]

The score measuring how quickly the visible parts of a page are rendered. Calculated for load actions that are marked as key user actions.

Visually complete - load action (by key user action, browser) [web]

The time taken to fully render content in the viewport. Calculated for load actions that are marked as key user actions.

Visually complete - XHR action (by key user action, browser) [web]

The time taken to fully render content in the viewport. Calculated for XHR actions that are marked as key user actions.

Error count (by key user action, user type, error type, error origin) [web]

The number of detected errors that occurred during key user actions.

User action count with errors (by key user action, user type) [web]

The number of key user actions with detected errors.

JavaScript errors count during user actions (by key user action, user type) [web]

The number of detected JavaScript errors that occurred during key user actions.

JavaScript error count without user actions (by key user action, user type) [web]

The number of detected standalone JavaScript errors (occurred between key user actions).

User action rate - affected by errors (by key user action, user type) [web]

The percentage of key user actions with detected errors.

Action count - custom action (by browser) [web]

The number of custom actions.

Action count - load action (by browser) [web]

The number of load actions.

Action count - XHR action (by browser) [web]

The number of XHR actions.

Action count (by Apdex category) [web]

The number of user actions.

Action with key performance metric count (by action type, geolocation, user type) [web]

The number of user actions that have a key performance metric and mapped geolocation.

Action duration - custom action (by browser) [web]

The duration of custom actions.

Action duration - load action (by browser) [web]

The duration of load actions.

Action duration - XHR action (by browser) [web]

The duration of XHR actions.

Actions per session average (by users, user type) [web]

The average number of user actions per user session.

Session count - estimated active sessions (by users, user type) [web]

The estimated number of active user sessions. An active session is one in which a user has been confirmed to still be active at a given time. For this high-cardinality metric, the HyperLogLog algorithm is used to approximate the session count.

User count - estimated active users (by users, user type) [web]

The estimated number of unique active users. For this high-cardinality metric, the HyperLogLog algorithm is used to approximate the user count.

User action rate - affected by JavaScript errors (by user type) [web]

The percentage of user actions with detected JavaScript errors.

Apdex (by user type) [web]

Apdex (by geolocation, user type) [web]

The average Apdex rating for user actions that have a mapped geolocation.

Bounce rate (by users, user type) [web]

The percentage of sessions in which users viewed only a single page and triggered only a single web request. Calculated by dividing single-page sessions by all sessions.

Conversion rate - sessions (by users, user type) [web]

The percentage of sessions in which at least one conversion goal was reached. Calculated by dividing converted sessions by all sessions.

Session count - converted sessions (by users, user type) [web]

The number of sessions in which at least one conversion goal was reached.

Cumulative Layout Shift - load action (by user type) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions.

Cumulative Layout Shift - load action (by geolocation, user type) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions.

Cumulative Layout Shift - load action (by browser) [web]

The score measuring the unexpected shifting of visible webpage elements. Calculated for load actions.

DOM interactive - load action (by browser) [web]

The time taken until a page's status is set to "interactive" and it's ready to receive user input. Calculated for load actions.

Session count - estimated ended sessions (by users, user type) [web]

The number of completed user sessions.

Rage click count [web]

The number of detected rage clicks.

Time to first byte - load action (by browser) [web]

The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Calculated for load actions.

Time to first byte - XHR action (by browser) [web]

The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Calculated for XHR actions.

First Input Delay - load action (by user type) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions.

First Input Delay - load action (by geolocation, user type) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions.

First Input Delay - load action (by browser) [web]

The time from the first interaction with a page to when the user agent can respond to that interaction. Calculated for load actions.

Largest Contentful Paint - load action (by user type) [web]

The time taken to render the largest element in the viewport. Calculated for load actions.

Largest Contentful Paint - load action (by geolocation, user type) [web]

The time taken to render the largest element in the viewport. Calculated for load actions.

Largest Contentful Paint - load action (by browser) [web]

The time taken to render the largest element in the viewport. Calculated for load actions.

Load event end - load action (by browser) [web]

The time taken to complete the load event of a page. Calculated for load actions.

Load event start - load action (by browser) [web]

The time taken to begin the load event of a page. Calculated for load actions.

Network contribution - load action (by user type) [web]

The time taken to request and receive resources (including DNS lookup, redirect, and TCP connect time). Calculated for load actions.

Network contribution - XHR action (by user type) [web]

The time taken to request and receive resources (including DNS lookup, redirect, and TCP connect time). Calculated for XHR actions.

Response end - load action (by browser) [web]

(AKA HTML downloaded) The time taken until the user agent receives the last byte of the response or the transport connection is closed, whichever comes first. Calculated for load actions.

Response end - XHR action (by browser) [web]

The time taken until the user agent receives the last byte of the response or the transport connection is closed, whichever comes first. Calculated for XHR actions.

Server contribution - load action (by user type) [web]

The time spent on server-side processing for a page. Calculated for load actions.

Server contribution - XHR action (by user type) [web]

The time spent on server-side processing for a page. Calculated for XHR actions.

Session duration (by users, user type) [web]

The average duration of user sessions.

Speed index - load action (by browser) [web]

The score measuring how quickly the visible parts of a page are rendered. Calculated for load actions.

Session count - estimated started sessions (by users, user type) [web]

The number of started user sessions.

Visually complete - load action (by browser) [web]

The time taken to fully render content in the viewport. Calculated for load actions.

Visually complete - XHR action (by browser) [web]

The time taken to fully render content in the viewport. Calculated for XHR actions.

Error count (by user type, error type, error origin) [web]

The number of detected errors.

Error count during user actions (by user type, error type, error origin) [web]

The number of detected errors that occurred during user actions.

Standalone error count (by user type, error type, error origin) [web]

The number of detected standalone errors (occurred between user actions).

User action count - with errors (by user type) [web]

The number of key user actions with detected errors.

Error count for Davis (by user type, error type, error origin, error context)) [web]

The number of errors that were included in Davis AI problem detection and analysis.

JavaScript error count - during user actions (by user type) [web]

The number of detected JavaScript errors that occurred during user actions.

JavaScript error count - without user actions (by user type) [web]

The number of detected standalone JavaScript errors (occurred between user actions).

User action rate - affected by errors (by user type) [web]

The percentage of user actions with detected errors.

Apdex (by OS, geolocation) [mobile, custom]

The Apdex rating for all captured user actions.

Apdex (by OS, app version) [mobile, custom]

The Apdex rating for all captured user actions.

User count - estimated users affected by crashes (by OS) [mobile, custom]

The estimated number of unique users affected by a crash. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

User count - estimated users affected by crashes (by OS, app version) [mobile, custom]

The estimated number of unique users affected by a crash. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

User rate - estimated users affected by crashes (by OS) [mobile, custom]

The estimated percentage of unique users affected by a crash. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

Crash count (by OS, geolocation) [mobile, custom]

The number of detected crashes.

Crash count (by OS, app version) [mobile, custom]

The number of detected crashes.

Crash count (by OS, app version) [mobile, custom]

The number of detected crashes.

User rate - estimated crash free users (by OS) [mobile, custom]

The estimated percentage of unique users not affected by a crash. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

Apdex (by key user action, OS) [mobile, custom]

The Apdex rating for all captured key user actions.

Action count (by key user action, OS, Apdex category) [mobile, custom]

The number of captured key user actions.

Action duration (by key user action, OS) [mobile, custom]

The duration of key user actions.

Reported error count (by key user action, OS) [mobile, custom]

The number of reported errors for key user actions.

Request count (by key user action, OS) [mobile, custom]

The number of captured web requests associated with key user actions.

Request duration (by key user action, OS) [mobile, custom]

The duration of web requests for key user actions. Be aware that this metric is measured in microseconds while other request duration metrics for mobile and custom apps are measured in milliseconds.

Request error count (by key user action, OS) [mobile, custom]

The number of detected web request errors for key user actions.

Request error rate (by key user action, OS) [mobile, custom]

The percentage of web requests with detected errors for key user actions

New user count (by OS) [mobile, custom]

The number of users that launched the application(s) for the first time. The metric is tied to specific devices, so users are counted multiple times if they install the application on multiple devices. The metric doesn't distinguish between multiple users that share the same device and application installation.

Request count (by OS, provider) [mobile, custom]

The number of captured web requests.

Request count (by OS, app version) [mobile, custom]

The number of captured web requests.

Request error count (by OS, provider) [mobile, custom]

The number of detected web request errors.

Request error count (by OS, app version) [mobile, custom]

The number of detected web request errors.

Request error rate (by OS, provider) [mobile, custom]

The percentage of web requests with detected errors.

Request error rate (by OS, app version) [mobile, custom]

The percentage of web requests with detected errors.

Request duration (by OS, provider) [mobile, custom]

The duration of web requests.

Request duration (by OS, app version) [mobile, custom]

The duration of web requests.

Session count (by agent version, OS) [mobile, custom]

The number of captured user sessions.

Session count (by OS, crash reporting level) [mobile, custom]

The number of captured user sessions.

Session count (by OS, data collection level) [mobile, custom]

The number of captured user sessions.

Session count - estimated (by OS, geolocation) [mobile, custom]

The estimated number of captured user sessions. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of sessions.

Session count (by OS, app version) [mobile, custom]

The number of captured user sessions.

Action count (by geolocation, Apdex category) [mobile, custom]

The number of captured user actions.

Action count (by OS, Apdex category) [mobile, custom]

The number of captured user actions.

Action count (by OS, app version) [mobile, custom]

The number of captured user actions.

Action duration (by OS, app version) [mobile, custom]

The duration of user actions.

User count - estimated (by OS, geolocation) [mobile, custom]

The estimated number of unique users that have a mapped geolocation. The metric is based on 'internalUserId'. When 'dataCollectionLevel' is set to 'performance' or 'off', 'internalUserId' is changed at each app start. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

User count - estimated (by OS, app version) [mobile, custom]

The estimated number of unique users. The metric is based on 'internalUserId'. When 'dataCollectionLevel' is set to 'performance' or 'off', 'internalUserId' is changed at each app start. For this high cardinality metric, the HyperLogLog algorithm is used to approximate the number of users.

Session count - billed and unbilled [custom]

The number of billed and unbilled user sessions. To get only the number of billed sessions, set the "Type" filter to "Billed".

Total user action and session properties

The number of billed user action and user session properties.

Session count - billed and unbilled - with Session Replay [mobile]

The number of billed and unbilled user sessions that include Session Replay data. To get only the number of billed sessions, set the "Type" filter to "Billed".

Session count - billed and unbilled [mobile]

The total number of billed and unbilled user sessions (with and without Session Replay data). To get only the number of billed sessions, set the "Type" filter to "Billed".

Total user action and session properties

The number of billed user action and user session properties.

Session count - billed and unbilled - with Session Replay [web]

The number of billed and unbilled user sessions that include Session Replay data. To get only the number of billed sessions, set the "Type" filter to "Billed".

Session count - billed and unbilled - without Session Replay [web]

The number of billed and unbilled user sessions that do not include Session Replay data. To get only the number of billed sessions, set the "Type" filter to "Billed".

Total user action and session properties

The number of billed user action and user session properties.

(DPS) Total Custom Events Classic billing usage

The number of custom events ingested aggregated over all monitored entities. Custom events include events sent to Dynatrace via the Events API or events created by a log event extraction rule. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Custom Events Classic billing usage by monitored entity

The number of custom events ingested split by monitored entity. Custom events include events sent to Dynatrace via the Events API or events created by a log event extraction rule. For details on the events billed, refer to the usage_by_event_info metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Custom Events Classic billing usage by event info

The number of custom events ingested split by event info. Custom events include events sent to Dynatrace via the Events API or events created by a log event extraction rule. The info contains the context of the event plus the configuration ID. For details on the related monitored entities, refer to the usage_by_entity metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Recorded metric data points per metric key

The number of reported metric data points split by metric key. This metric does not account for included metric data points available to your environment.

(DPS) Total billed metric data points

The total number of metric data points after deducting the included metric data points. This is the rate-card value used for billing. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Total metric data points billable for Foundation & Discovery hosts

The number of metric data points billable for Foundation & Discovery hosts.

(DPS) Total metric data points billed for Full-Stack hosts

The number of metric data points billed for Full-Stack hosts. To view the unadjusted usage per host, use builtin:billing.full_stack_monitoring.metric_data_points.ingested_by_host . This trailing metric is reported at 15-minute intervals with up to a 15-minute delay.

(DPS) Total metric data points billed for Infrastructure-monitored hosts

The number of metric data points billed for Infrastructure-monitored hosts. To view the unadjusted usage per host, use builtin:billing.infrastructure_monitoring.metric_data_points.ingested_by_host . This trailing metric is reported at 15-minute intervals with up to a 15-minute delay.

(DPS) Total metric data points billed by other entities

The number of metric data points billed that cannot be assigned to a host. The values reported in this metric are not eligible for included metric deduction and will be billed as is. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. o view the monitored entities that consume this usage, use the other_by_entity metric.

(DPS) Billed metric data points reported and split by other entities

The number of billed metric data points split by entities that cannot be assigned to a host. The values reported in this metric are not eligible for included metric deduction and will be billed as is. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Custom Traces Classic billing usage

The number of spans ingested aggregated over all monitored entities. A span is a single operation within a distributed trace, ingested into Dynatrace. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Custom Traces Classic billing usage by monitored entity

The number of spans ingested split by monitored entity. A span is a single operation within a distributed trace, ingested into Dynatrace. For details on span types, refer to the usage_by_span_type metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Custom Traces Classic billing usage by span type

The number of spans ingested split by span type. A span is a single operation within a distributed trace, ingested into Dynatrace. Span kinds can be CLIENT, SERVER, PRODUCER, CONSUMER or INTERNAL For details on the related monitored entities, refer to the usage_by_entity metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

DDU events consumption by event info

License consumption of Davis data units by events pool split by event info

DDU events consumption by monitored entity

License consumption of Davis data units by events pool split by monitored entity

Total DDU events consumption

Sum of license consumption of Davis data units aggregated over all monitored entities for the events pool

DDU log consumption by log path

License consumption of Davis data units by log pool split by log path

DDU log consumption by monitored entity

License consumption of Davis data units by log pool split by monitored entity

Total DDU log consumption

Sum of license consumption of Davis data units aggregated over all logs for the log pool

DDU metrics consumption by monitored entity

License consumption of Davis data units by metrics pool split by monitored entity

DDU metrics consumption by monitored entity w/o host-unit included DDUs

License consumption of Davis data units by metrics pool split by monitored entity (aggregates host-unit included metrics, so value might be higher than actual consumption)

Reported metrics DDUs by metric key

Reported Davis data units usage by metrics pool split by metric key

Total DDU metrics consumption

Sum of license consumption of Davis data units aggregated over all metrics for the metrics pool

DDU serverless consumption by function

License consumption of Davis data units by serverless pool split by Amazon Resource Names (ARNs)

DDU serverless consumption by service

License consumption of Davis data units by serverless pool split by service

Total DDU serverless consumption

Sum of license consumption of Davis data units aggregated over all services for the serverless pool

DDU traces consumption by span type

License consumption of Davis data units by traces pool split by SpanKind, as defined in OpenTelemetry specification

DDU traces consumption by monitored entity

License consumption of Davis data units by traces pool split by monitored entity

Total DDU traces consumption

Sum of license consumption of Davis data units aggregated over all monitored entities for the traces pool

DDU included per host

Included Davis data units per host

DDU included metric data points per host

Included metric data points per host

(DPS) Business events usage - Ingest & Process

Business events Ingest & Process usage, tracked as bytes ingested within the hour. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Business events usage - Query

Business events Query usage, tracked as bytes read within the hour. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Business events usage - Retain

Business events Retain usage, tracked as total storage used within the hour, in bytes. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Ingested metric data points for Foundation & Discovery

The number of metric data points aggregated over all Foundation & Discovery hosts.

(DPS) Ingested metric data points for Foundation & Discovery per host

The number of metric data points split by Foundation & Discovery hosts.

(DPS) Foundation & Discovery billing usage

The total number of host-hours being monitored by Foundation & Discovery, counted in 15 min intervals.

(DPS) Foundation & Discovery billing usage per host

The host-hours being monitored by Foundation & Discovery, counted in 15 min intervals.

(DPS) Available included metric data points for Full-Stack hosts

The total number of included metric data points that can be deducted from the metric data points reported by Full-Stack hosts. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view the number of applied included metric data points, use builtin:billing.full_stack_monitoring.metric_data_points.included_used . If the difference between this metric and the applied metrics is greater than 0, then more metrics can be ingested using Full-Stack Monitoring without incurring additional costs.

(DPS) Used included metric data points for Full-Stack hosts

The number of consumed included metric data points per host monitored with Full-Stack Monitoring. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view the number of potentially available included metrics, use builtin:billing.full_stack_monitoring.metric_data_points.included_used . If the difference between this metric and the available metrics is greater than zero, then that means that more metrics could be ingested on Full-Stack hosts without incurring additional costs.

(DPS) Total metric data points reported by Full-Stack hosts

The number of metric data points aggregated over all Full-Stack hosts. The values reported in this metric are eligible for included-metric-data-point deduction. Use this total metric to query longer timeframes without losing precision or performance. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view usage on a per-host basis, use builtin:billing.full_stack_monitoring.metric_data_points.ingested_by_host .

(DPS) Metric data points reported and split by Full-Stack hosts

The number of metric data points split by Full-Stack hosts. The values reported in this metric are eligible for included-metric-data-point deduction. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. The pool of available included metrics for a "15-minute interval" is visible via builtin:billing.full_stack_monitoring.metric_data_points.included . To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Full-Stack Monitoring billing usage

The total GiB memory of hosts being monitored in full-stack mode, counted in 15 min intervals. Use this total metric to query longer timeframes without losing precision or performance. For details on the hosts causing the usage, refer to the usage_per_host metric. For details on the containers causing the usage, refer to the usage_per_container metric.

(DPS) Full-Stack Monitoring billing usage per host

The GiB memory per host being monitored in full-stack mode, counted in 15 min intervals. For example, a host with 8 GiB of RAM monitored for 1 hour has 4 data points with a value of 2. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Available included metric data points for Infrastructure-monitored hosts

The total number of included metric data points that can be deducted from the metric data points reported by Infrastructure-monitored hosts. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view the number of applied included metric data points, use builtin:billing.infrastructure_monitoring.metric_data_points.included_used . If the difference between this metric and the applied metrics is greater than zero, then that means that more metrics could be ingested on Infrastructure-monitored hosts without incurring additional costs.

(DPS) Used included metric data points for Infrastructure-monitored hosts

The number of consumed included metric data points for Infrastructure-monitored hosts. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view the number of potentially available included metrics, use builtin:billing.infrastructure_monitoring.metric_data_points.included_used . If the difference between this metric and the available metrics is greater than zero, then that means that more metrics could be ingested on Infrastructure-monitored hosts without incurring additional costs.

(DPS) Total metric data points reported by Infrastructure-monitored hosts

The number of metric data points aggregated over all Infrastructure-monitored hosts. The values reported in this metric are eligible for included-metric-data-point deduction. Use this total metric to query longer timeframes without losing precision or performance. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. To view usage on a per-host basis, use the builtin:billing.full_stack_monitoring.metric_data_points.ingested_by_host .

(DPS) Metric data points reported and split by Infrastructure-monitored hosts

The number of metric data points split by Infrastructure-monitored hosts. The values reported in this metric are eligible for included-metric-data-point deduction. This trailing metric is reported at 15-minute intervals with up to a 15-minute delay. The pool of available included metrics for a "15-minute interval" is visible via builtin:billing.infrastructure_monitoring.metric_data_points.included . To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Infrastructure Monitoring billing usage

The total number of host-hours being monitored in infrastructure-only mode, counted in 15 min intervals. Use this total metric to query longer timeframes without losing precision or performance. For details on the hosts causing the usage, refer to the usage_per_host metric.

(DPS) Infrastructure Monitoring billing usage per host

The host-hours being monitored in infrastructure-only mode, counted in 15 min intervals. A host monitored for the whole hour has 4 data points with a value of 0.25, regardless of the memory size. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Log Management and Analytics usage - Ingest & Process

Log Management and Analytics Ingest & Process usage, tracked as bytes ingested within the hour. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Log Management and Analytics usage - Query

Log Management and Analytics Query usage, tracked as bytes read within the hour. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Log Management and Analytics usage - Retain

Log Management and Analytics Retain usage, tracked as total storage used within the hour, in bytes. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay.

(DPS) Total Log Monitoring Classic billing usage

The number of log records ingested aggregated over all monitored entities. A log record is recognized by either a timestamp or a JSON object. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Log Monitoring Classic billing usage by monitored entity

The number of log records ingested split by monitored entity. A log record is recognized by either a timestamp or a JSON object. For details on the log path, refer to the usage_by_log_path metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Log Monitoring Classic billing usage by log path

The number of log records ingested split by log path. A log record is recognized by either a timestamp or a JSON object. For details on the related monitored entities, refer to the usage_by_entity metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Mainframe Monitoring billing usage

The total number of MSU-hours being monitored, counted in 15 min intervals.

(DPS) Total Real-User Monitoring Property (mobile) billing usage

(Mobile) User action and session properties count. For details on how usage is calculated, refer to the documentation or builtin:billing.real_user_monitoring.web.property.usage_by_application . Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Real-User Monitoring Property (mobile) billing usage by application

(Mobile) User action and session properties count by application. The billed value is calculated based on the number of sessions reported in builtin:billing.real_user_monitoring.mobile.session.usage_by_app + builtin:billing.real_user_monitoring.mobile.session_with_replay.usage_by_app . plus the number of configured properties that exceed the included number of properties (free of charge) offered for a given application. Data points are only written for billed sessions. If the value is 0, you have available metric data points. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Real-User Monitoring (mobile) billing usage

(Mobile) Session count without Session Replay. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions end during the same minute, then the values are added together. Use this total metric to query longer timeframes without losing precision or performance. To view the application that consume this usage, refer to the usage_by_app metric.

(DPS) Real-User Monitoring (mobile) billing usage by application

(Mobile) Session count without Session Replay split by application The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions of the same application end during the same minute, then the values are added together. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Real-User Monitoring (mobile) with Session Replay billing usage

(Mobile) Session count with Session Replay. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions end during the same minute, then the values are added together. Use this total metric to query longer timeframes without losing precision or performance. To view the application that consume this usage, refer to the usage_by_app metric.

(DPS) Real-User Monitoring (mobile) with Session Replay billing usage by application

(Mobile) Session count with Session Replay split by application. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions of the same application end during the same minute, then the values are added together. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Real-User Monitoring Property (web) billing usage

(Web) User action and session properties count. For details on how usage is calculated, refer to the documentation or builtin:billing.real_user_monitoring.web.property.usage_by_application . Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Real-User Monitoring Property (web) billing usage by application

(Web) User action and session properties count by application. The billed value is calculated based on the number of sessions reported in builtin:billing.real_user_monitoring.web.session.usage_by_app + builtin:billing.real_user_monitoring.web.session_with_replay.usage_by_app . plus the number of configured properties that exceed the included number of properties (free of charge) offered for a given application. Data points are only written for billed sessions. If the value is 0, you have available metric data points. This trailing metric is reported hourly for the previous hour. Metric values are reported with up to a one-hour delay. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Real-User Monitoring (web) billing usage

(Web) Session count without Session Replay. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions end during the same minute, then the values are added together. Use this total metric to query longer timeframes without losing precision or performance. To view the application that consume this usage, refer to the usage_by_app metric.

(DPS) Real-User Monitoring (web) billing usage by application

(Web) Session count without Session Replay split by application. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions of the same application end during the same minute, then the values are added together. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Real-User Monitoring (web) with Session Replay billing usage

(Web) Session count with Session Replay. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions end during the same minute, then the values are added together. Use this total metric to query longer timeframes without losing precision or performance. To view the application that consume this usage, refer to the usage_by_app metric.

(DPS) Real-User Monitoring (web) with Session Replay billing usage by application

(Web) Session count with Session Replay split by application. The value billed for each session is the session duration measured in hours. So a 3-hour session results in a single data-point value of 3. If two sessions of the same application end during the same minute, then the values are added together. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Runtime Application Protection billing usage

Total GiB-memory of hosts protected with Runtime Application Protection (Application Security), counted at 15-minute intervals. Use this total metric to query longer timeframes without losing precision or performance. For details on the monitored hosts, refer to the usage_per_host metric.

(DPS) Runtime Application Protection billing usage per host

GiB-memory per host protected with Runtime Application Protection (Application Security), counted at 15-minute intervals. For example, a host with 8 GiB of RAM monitored for 1 hour has 4 data points with a value of 2. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Runtime Vulnerability Analytics billing usage

Total GiB-memory of hosts protected with Runtime Vulnerability Analytics (Application Security), counted at 15-minute intervals. Use this total metric to query longer timeframes without losing precision or performance. For details on the monitored hosts, refer to the usage_per_host metric.

(DPS) Runtime Vulnerability Analytics billing usage per host

GiB-memory per hosts protected with Runtime Vulnerability Analytics (Application Security), counted at 15-minute intervals. For example, a host with 8 GiB of RAM monitored for 1 hour has 4 data points with a value of 2. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Total Serverless Functions Classic billing usage

The number of invocations of the serverless function aggregated over all monitored entities. The term "function invocations" is equivalent to "function requests" or "function executions". Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Serverless Functions Classic billing usage by monitored entity

The number of invocations of the serverless function split by monitored entity. The term "function invocations" is equivalent to "function requests" or "function executions". For details on which functions are invoked, refer to the usage_by_function metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

(DPS) Serverless Functions Classic billing usage by function

The number of invocations of the serverless function split by function. The term "function invocations" is equivalent to "function requests" or "function executions". For details on the related monitored entities, refer to the usage_by_entity metric. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

Actions

The number of billed actions consumed by browser monitors.

(DPS) Total Browser Monitor or Clickpath billing usage

The number of synthetic actions which triggers a web request that includes a page load, navigation event, or action that triggers an XHR or Fetch request. Scroll downs, keystrokes, or clicks that don't trigger web requests aren't counted as such actions. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Browser Monitor or Clickpath billing usage per synthetic browser monitor

The number of synthetic actions which triggers a web request that includes a page load, navigation event, or action that triggers an XHR or Fetch request. Scroll downs, keystrokes, or clicks that don't trigger web requests aren't counted as such actions. Actions are split by the Synthetic Browser Monitors that caused them. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

Third-party results

The number of billed results consumed by third-party monitors.

(DPS) Total Third-Party Synthetic API Ingestion billing usage

The number of synthetic test results pushed into Dynatrace with Synthetic 3rd party API. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) Third-Party Synthetic API Ingestion billing usage per external browser monitor

The number of synthetic test results pushed into Dynatrace with Synthetic 3rd party API. The ingestions are split by external Synthetic Browser Monitors for which the results where ingested. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

Requests

The number of billed requests consumed by HTTP monitors.

(DPS) Total HTTP monitor billing usage

The number of HTTP requests performed during execution of synthetic HTTP monitor. Use this total metric to query longer timeframes without losing precision or performance.

(DPS) HTTP monitor billing usage per HTTP monitor

The number of HTTP requests performed, split by synthetic HTTP monitor. To improve performance and avoid exceeding query limits when working with longer timeframes, use the total metric.

ALB number of active connections

ALB number of new connections

ALB number of 4XX errors

ALB number of 5XX errors

ALB number of 4XX target errors

ALB number of 5XX target errors

ALB number of rejected connections

ALB number of target connection errors

ALB number of client TLS negotiation errors

ALB number of processed bytes

ALB number of consumed LCUs

ALB number of requests

ALB target response time

Number of running EC2 instances (ASG)

Number of stopped EC2 instances (ASG)

Number of terminated EC2 instances (ASG)

Number of running EC2 instances (AZ)

Number of stopped EC2 instances (AZ)

Number of terminated EC2 instances (AZ)

DynamoDB read capacity units

DynamoDB write capacity units

DynamoDB provisioned read capacity units

DynamoDB provisioned write capacity units

DynamoDB read capacity units %

DynamoDB write capacity units %

DynamoDB number of requests with HTTP 500 status code

DynamoDB number of requests with HTTP 400 status code

DynamoDB number of successful request latency for operation

DynamoDB number of items returned by operation

DynamoDB number of throttled requests for operation

DynamoDB number of read throttled events

DynamoDB number of write throttled events

Number of tables for AvailabilityZone

EBS volume read latency

EBS volume write latency

EBS volume consumed OPS

EBS volume read OPS

EBS volume write OPS

EBS volume throughput %

EBS volume read throughput

EBS volume write throughput

EBS volume idle time %

EBS volume queue length

EC2 CPU usage %

EC2 instance storage read IOPS

EC2 instance storage read rate

EC2 instance storage write IOPS

EC2 instance storage write rate

EC2 network data received rate

EC2 network data transmitted rate

CLB backend connection errors

CLB number of backend 2XX errors

CLB number of backend 3XX errors

CLB number of backend 4XX errors

CLB number of backend 5XX errors

CLB number of 4XX errors

CLB number of 5XX errors

CLB frontend errors percentage

CLB number of healthy hosts

CLB number of unhealthy hosts

CLB latency

CLB number of completed requests

LambdaFunction concurrent executions count

LambdaFunction code execution time.

LambdaFunction number of failed invocations with HTTP 4XX status code

LambdaFunction rate of failed invocations to all invocations %

LambdaFunction number of times a function is invoked

LambdaFunction provisioned concurrent executions count

LambdaFunction provisioned concurrency invocation count

LambdaFunction provisioned concurrency spillover invocation count

LambdaFunction throttled function invocation count

NLB number of active flows

NLB number of new flows

NLB number of client resets

NLB number of resets

NLB number of target resets

NLB number of processed bytes

NLB number of consumed LCUs

RDS CPU usage %

RDS read latency

RDS write latency

RDS freeable memory

RDS swap usage

RDS network received throughput

RDS network transmitted throughput

RDS read IOPS

RDS write IOPS

RDS read throughput

RDS write throughput

RDS connections

RDS free storage space %

RDS restarts

Failed requests

Other requests

Successful requests

Total requests

Unauthorized requests

Capacity

Duration

Healthy host count

Unhealthy host count

Requests failed

Requests total

Response status

Current connections count

Network throughput

Requests in application queue

Requests in application queue

Function execution count

Function execution units count

HTTP 5xx

IO other operations/s

IO read operations/s

IO write operations/s

IO other bytes/s

IO read bytes/s

IO write bytes/s

Received bytes

Sent bytes

HTTP 2xx

HTTP 403

HTTP 5xx

IO other operations/s

IO read operations/s

IO write operations/s

IO other bytes/s

IO read bytes/s

IO write bytes/s

Response time avg

Received bytes

Sent bytes

Requests count

Available Storage

Data Usage

Document Count

Document Quota

Index Usage

Metadata Requests

Normalized request units consumption

Provisioned Throughput

Replication Latency

Total number of request units

Total number of requests

Service Availability

Capture backlog

Captured bytes

Captured messages

Quota exceeded errors

Server errors

User errors

Incoming requests

Successful requests

Throttled requests

Incoming bytes

Outgoing bytes

Incoming messages

Outgoing messages

Active connections

Closed connections

Opened connections

Commands abandoned

Commands completed

Commands rejected

Connected devices

Number of throttling errors

Total device data usage

Total devices

Messages delivered to the built-in endpoint (messages/events)

Message latency for the built-in endpoint (messages/events)

Messages delivered to Event Hub endpoints

Message latency for event hub endpoints

Dropped messages

Invalid messages

Orphaned messages

Telemetry message send attempts

Telemetry messages sent

Messages matching fallback condition

Message latency for service bus queue endpoints

Messages delivered to service bus queue endpoints

Message latency for service bus topic endpoints

Messages delivered to service bus topic endpoints

Message latency for storage endpoints

Blobs written to storage

Data written to storage

Messages delivered to storage endpoints

Load balancer DIP TCP availability

Load balancer DIP UDP availability

Load Balancer VIP availability

SNAT connections successful

SNAT connections pending

SNAT connections failed

Bytes received

Bytes sent

Packets received

Packets sent

SYN packets received

SYN packets sent

Cache hits

Cache misses

Read bytes/s

Write bytes/s

Get commands

Set commands

Total no. of processed commands

No. of evicted keys

No. of expired keys

Total no. of keys

Used memory

Used memory RSS

Connected clients

Server load