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.

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

The number of all reported errors.

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

The number of captured user sessions.

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 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

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.

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.

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) 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.

(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.

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.

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.

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) 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.

Number of running EC2 instances (AZ)

Number of starting VMs in region

Number of active VMs in region

Number of stopped VMs in region

Number of starting VMs in scale set

Number of active VMs in scale set

Number of stopped VMs in scale set

CF: Time to fetch cell states

The time that the auctioneer took to fetch state from all the cells when running its auction.

CF: App instance placement failures

The number of application instances that the auctioneer failed to place on Diego cells.

CF: App instance starts

The number of application instances that the auctioneer successfully placed on Diego cells.

CF: Task placement failures

The number of tasks that the auctioneer failed to place on Diego cells.

CF: 502 responses

The number of responses that indicate invalid service responses produced by an application.

CF: Response latency

The average response time from the application to clients.

CF: 5xx responses

The number of responses that indicate repeatedly crashing apps or response issues from applications.

CF: Total requests

The number of all requests representing the overall traffic flow.

CPU usage

Disk allocation

Disk capacity

Memory resident

Memory usage

Network incoming bytes rate

Network outgoing bytes rate

Host CPU usage %

Host disk usage rate

Host disk commands aborted

Host disk queue latency

Host disk read IOPS

Host disk read latency

Host disk read rate

Host disk write IOPS

Host disk write latency

Host disk write rate

Host compression rate

Host memory consumed

Host decompression rate

Host swap in rate

Host swap out rate

Host network data received rate

Host network data transmitted rate

Data received rate

Data transmitted rate

Packets received dropped

Packets transmitted dropped

Number of VMs

Number of VMs powered-off

Number of VMs suspended

Host availability %

VM CPU ready %

VM swap wait

VM CPU usage MHz

VM CPU usage %

VM disk usage rate

VM memory active

VM compression rate

VM memory consumed

VM decompression rate

VM swap in rate

VM swap out rate

VM network data received rate

VM network data transmitted rate

Containers: CPU throttling, mCores

CPU throttling per container in millicores.

[Deprecated] Containers: CPU throttling, mCores

CPU throttling per container in millicores. Deprecated metric for historical data access only. For regular access, use builtin:containers.cpu.throttledMilliCores instead.

Containers: CPU usage, mCores

CPU usage per container in millicores

[Deprecated] Containers: CPU usage, mCores

CPU usage per container in millicores. Deprecated metric for historical data access only. For regular access, use builtin:containers.cpu.usageMilliCores instead.

Containers: CPU usage, % of limit

Percent CPU usage per container relative to CPU resource limit. Logical cores are used if CPU limit isn't set.

[Deprecated] Containers: CPU usage, % of limit

Percent CPU usage per container relative to CPU resource limit. Logical cores is used if CPU limit is not set. Deprecated metric for historical data access only. For regular access, use builtin:containers.cpu.usagePercent instead.

Containers: CPU limit, mCores

CPU resource limit per container in millicores.

Containers: CPU logical cores

Number of logical CPU cores of the host.

Containers: CPU shares

Number of CPU shares allocated per container.

Containers: CPU throttled time, ns/min

Total amount of time a container has been throttled, in nanoseconds per minute.

[Deprecated] Containers: CPU throttling ratio

CPU resource limit per container.

Containers: CPU system usage, mCores

CPU system usage per container in millicores.

Containers: CPU system usage time, ns/min

Used system time per container in nanoseconds per minute.

Containers: CPU usage time, ns/min

Sum of used system and user time per container in nanoseconds per minute.

Containers: CPU user usage, mCores

CPU user usage per container in millicores.

Containers: CPU user usage time, ns/min

Used user time per container in nanoseconds per minute.

Containers: Memory usage, bytes

Resident set size (Linux) or private working set size (Windows) per container in bytes.

[Deprecated] Containers: Memory usage, bytes

Resident set size (Linux) or private working set size (Windows) per container in bytes. Deprecated metric for historical data access only. For regular access, use builtin:containers.memory.residentSetBytes instead.

Containers: Memory usage, % of limit

Resident set size (Linux) or private working set size (Windows) per container in percent relative to container memory limit. If no limit is set, this equals total physical memory.

[Deprecated] Containers: Memory usage, % of limit

Resident set size (Linux) or private working set size (Windows) per container in percent relative to container memory limit. If no limit is set, this equals total physical memory. Deprecated metric for historical data access only. For regular access, use builtin:containers.memory.usagePercent instead.

Containers: Memory cache, bytes

Page cache memory per container in bytes.

Containers: Memory limit, bytes

Memory limit per container in bytes. If no limit is set, this is an empty value.

Containers: Memory limit, % of physical memory

Percent memory limit per container relative to total physical memory. If no limit is set, this is an empty value.

Containers: Memory - out of memory kills

Number of out of memory kills for a container.

Containers: Memory - total physical memory, bytes

Total physical memory on the host in bytes.

Container bytes received

Container bytes transmitted

Container cpu usage

Devicemapper data space available

Devicemapper data space used

Devicemapper meta-data space available

Devicemapper meta-data space used

Memory percent

Container memory usage

Number of containers launched

Number of containers running

Number of containers running

Number of containers terminated

Container throttled time

Dashboard view count

Host availability

Host availability state metric reported in 1 minute intervals

z/OS General CPU usage

z/OS Rolling 4 hour MSU average

z/OS MSU capacity

z/OS zIIP eligible time

AIX Entitlement configured

Capacity Entitlement is the number of virtual processors assigned to the AIX partition. It’s measured in fractions of processor equal to 0.1 or 0.01. See <a href="https://dt-url.net/3n234vz" >Assigning the appropriate processor entitled capacity</a> for more info about entitlement

AIX Entitlement used

Percentage of entitlement used. Capacity Entitlement is the number of virtual cores assigned to the AIX partition. See <a href="https://dt-url.net/3n234vz" >Assigning the appropriate processor entitled capacity</a> for more info about entitlement

CPU idle

Average CPU time, when the CPU didn't have anything to do

CPU I/O wait

Percentage of time when CPU was idle during which the system had an outstanding I/O request. It is not available on Windows.

System load

The average number of processes that are being executed by CPU or waiting to be executed by CPU over the last minute

System load15m

The average number of processes that are being executed by CPU or waiting to be executed by CPU over the last 15 minutes

System load5m

The average number of processes that are being executed by CPU or waiting to be executed by CPU over the last 5 minutes

CPU other

Average CPU time spent on other tasks: servicing interrupt requests (IRQ), running virtual machines under the control of the host's kernel (It means the host is a hypervisor for VMs). It's available only for Linux hosts

AIX Physical consumed

Total CPUs consumed by the AIX partition

CPU steal

Average CPU time, when a virtual machine waits to get CPU cycles from the hypervisor. In a virtual environment, CPU cycles are shared across virtual machines on the hypervisor server. If your virtualized host displays a high CPU steal, it means CPU cycles are being taken away from your virtual machine to serve other purposes. It may indicate an overloaded hypervisor. It's available only for Linux hosts

CPU system

Average CPU time when CPU was running in kernel mode

CPU usage %

Percentage of CPU time when CPU was utilized. A value close to 100% means most host processing resources are in use, and host CPUs can’t handle additional work

CPU user

Average CPU time when CPU was running in user mode

Number of DNS errors by type

The number of DNS errors by type

Number of orphaned DNS responses

The number of orphaned DNS responses on the host

Number of DNS queries

The number of DNS queries on the host

DNS query time sum

The time of all DNS queries on the host

DNS query time

The average time of DNS query. Calculated with DNS query time sum divided by number of DNS queries for each host and dns server pair.

DNS query time by DNS server

The weighted average time of DNS query by DNS server ip. Calculated with DNS query time sum divided by number of DNS queries. It weights the result taking into account number of requests from each host.

DNS query time on host

The weighted average time of DNS query on a host. Calculated with DNS query time sum divided by number of DNS queries on a host. It weights the result taking into account number of requests to each dns server

Disk throughput read

File system read throughput in bits per second

Disk throughput write

File system write throughput in bits per second

Disk available

Amount of free space available for user in file system. On Linux and AIX it is free space available for unprivileged user. It doesn't contain part of free space reserved for the root.

Disk read bytes per second

Speed of read from file system in bytes per second

Disk write bytes per second

Speed of write to file system in bytes per second

Disk available %

Percentage of free space available for user in file system. On Linux and AIX it is % of free space available for unprivileged user. It doesn't contain part of free space reserved for the root.

Inodes available %

Percentage of free inodes available for unprivileged user in file system. Metric not available on Windows.

Inodes total

Total amount of inodes available for unprivileged user in file system. Metric not available on Windows.

Disk average queue length

Average number of read and write operations in disk queue

Disk read operations per second

Number of read operations from file system per second

Disk read time

Average time of read from file system. It shows average disk latency during read.

Disk used

Amount of used space in file system

Disk used %

Percentage of used space in file system

Disk utilization time

Percent of time spent on disk I/O operations

Disk write operations per second

Number of write operations to file system per second

Disk write time

Average time of write to file system. It shows average disk latency during write.

File descriptors max

Maximum amount of file descriptors for use

File descriptors used

Amount of file descriptors used

AIX Kernel threads blocked

Length of the swap queue. The swap queue contains the threads ready to run but swapped out with the currently running threads

AIX Kernel threads I/O event wait

Number of threads that are waiting for file system direct (cio) + Number of processes that are asleep waiting for buffered I/O

AIX Kernel threads I/O message wait

Number of threads that are sleeping and waiting for raw I/O operations at a particular time. Raw I/O operation allows applications to direct write to the Logical Volume Manager (LVM) layer

AIX Kernel threads runnable

Number of runnable threads (running or waiting for run time) (threads ready). The average number of runnable threads is seen in the first column of the vmstat command output

Memory available

The amount of memory (RAM) available on the host. The memory that is available for allocation to new or existing processes. Available memory is an estimation of how much memory is available for use without swapping.

Memory available %

The percentage of memory (RAM) available on the host. The memory that is available for allocation to new or existing processes. Available memory is an estimation of how much memory is available for use without swapping. Shows available memory as percentages.

Page faults per second

The measure of the number of page faults per second on the monitored host. This value includes soft faults and hard faults.

Swap available

The amount of swap memory or swap space (also known as paging, which is the on-disk component of the virtual memory system) available.

Swap total

Amount of total swap memory or total swap space (also known as paging, which is the on-disk component of the virtual memory system) for use.

Swap used

The amount of swap memory or swap space (also known as paging, which is the on-disk component of the virtual memory system) used.

Kernel memory

The memory used by the system kernel. It includes memory used by core components of OS along with any device drivers.Typically, the number will be very small.

Memory reclaimable

The memory usage for specific purposes. Reclaimable memory is calculated as available memory (estimation of how much memory is available for use without swapping) minus free memory (amount of memory that is currently not used for anything). See <a href="https://dt-url.net/bx024wr" >the article</a> for more information on reclaimable memory.

Memory total

The amount of memory (RAM) installed on the system.

Memory used %

Shows percentage of memory currently used. Used memory is calculated by OneAgent as follows: used = total – available. So the used memory metric displayed in Dynatrace analysis views is not equal to the used memory metric displayed by system tools. At the same time, it’s important to remember that system tools report used memory the way they do due to historical reasons, and that this particular method of calculating used memory isn’t really representative of how the Linux kernel manages memory in modern systems. The difference in these measurements is in fact quite significant, too. Note: Calculated by taking 100% - "Memory available %".

Memory used

Used memory is calculated by OneAgent as follows: used = total – available. So the used memory metric displayed in Dynatrace analysis views is not equal to the used memory metric displayed by system tools. At the same time, it’s important to remember that system tools report used memory the way they do due to historical reasons, and that this particular method of calculating used memory isn’t really representative of how the Linux kernel manages memory in modern systems. The difference in these measurements is in fact quite significant, too.

NIC packets dropped

Network interface packets dropped on the host

NIC received packets dropped

Network interface received packets dropped on the host

NIC sent packets dropped

Network interface sent packets dropped on the host

NIC packet errors

Network interface packet errors on the host

NIC received packet errors

Network interface received packet errors on a host

NIC sent packet errors

Network interface sent packet errors on the host

NIC packets received

Network interface packets received on the host

NIC packets sent

Network interface packets sent on the host

NIC bytes received

Network interface bytes received on the host

NIC bytes sent on host

Network interface bytes sent on the host

NIC connectivity

Network interface connectivity on the host

NIC receive link utilization

Network interface receive link utilization on the host

NIC transmit link utilization

Network interface transmit link utilization on the host

NIC retransmission

Network interface retransmission on the host

NIC received packets retransmission

Network interface retransmission for received packets on the host

NIC sent packets retransmission

Network interface retransmission for sent packets on the host

Traffic

Network traffic on the host

Traffic in

Traffic incoming at the host

Traffic out

Traffic outgoing from the host

Host retransmission base received

Host aggregated process retransmission base received per second

Host retransmission base sent

Host aggregated process retransmission base sent per second

Host retransmitted packets received

Host aggregated process retransmitted packets received per second

Host retransmitted packets sent

Host aggregated process retransmitted packets sent per second

Localhost session reset received

Host aggregated session reset received per second on localhost

Localhost session timeout received

Host aggregated session timeout received per second on localhost

Localhost new session received

Host aggregated new session received per second on localhost

Host session reset received

Host aggregated process session reset received per second

Host session timeout received

Host aggregated process session timeout received per second

Host new session received

Host aggregated process new session received per second

Host bytes received

Host aggregated process bytes received per second

Host bytes sent

Host aggregated process bytes sent per second

OS Service availability

This metric provides the status of the OS service. If the OS service is running, the OS module is reporting "1" as a value of the metric. In any other case, the metric has a value of "0"Please note that this metric provides data only from Classic Windows services monitoring (supported only on Windows), currently replaced by the new OS Services monitoring. Learn more about Classic Windows services monitoring: https://dt-url.net/classic-windows-services

OS Process count

This metric shows an average number of processes, over one minute, running on the host. The reported number of processes is based on processes detected by the OS module, read in 10 seconds cycles.

PGI count

This metric shows the number of PGIs created by the OS module every minute. It includes every PGI, even those which are considered not important and are not reported to Dynatrace.

Reported PGI count

This metric shows the number of PGIs created and reported by the OS module every minute. It includes only PGIs, which are considered important and reported to Dynatrace. Important PGIs are those in which OneAgent recognizes the technology, have open network ports, generate significant resource usage, or are created via Declarative process grouping rules. You can read more what makes process important at https://dt-url.net/most-important-processes

z/OS General CPU time

Total General CPU time per minute

z/OS Consumed MSUs per SMF interval (SMF70EDT)

Number of consumed MSUs per SMF interval (SMF70EDT)

z/OS zIIP time

Total zIIP time per minute

z/OS zIIP usage

Actively used zIIP as a percentage of available zIIP

Host availability %

Host availability %

Host uptime

Time since last host boot up. Requires OneAgent 1.259+. The metric is not supported for application-only OneAgent deployments.

Kubernetes: Cluster readyz status

Current status of the Kubernetes API server reported by the /readyz endpoint (0 or 1).

Kubernetes: Container - out of memory (OOM) kill count

This metric measures the out of memory (OOM) kills. The most detailed level of aggregation is container. The value corresponds to the status 'OOMKilled' of a container in the pod resource's container status. The metric is only written if there was at least one container OOM kill.

Kubernetes: Container - restart count

This metric measures the amount of container restarts. The most detailed level of aggregation is container. The value corresponds to the delta of the 'restartCount' defined in the pod resource's container status. The metric is only written if there was at least one container restart.

Kubernetes: Node conditions

This metric describes the status of a Kubernetes node. The most detailed level of aggregation is node.

Kubernetes: Node - CPU allocatable

This metric measures the total allocatable cpu. The most detailed level of aggregation is node. The value corresponds to the allocatable cpu of a node.

Kubernetes: Container - CPU throttled (by node)

This metric measures the total CPU throttling by container. The most detailed level of aggregation is node.

Kubernetes: Container - CPU usage (by node)

This metric measures the total CPU consumed (user usage + system usage) by container. The most detailed level of aggregation is node.

Kubernetes: Pod - CPU limits (by node)

This metric measures the effective cpu limits. The most detailed level of aggregation is node. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Pod - memory limits (by node)

This metric measures the effective memory limits. The most detailed level of aggregation is node. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Node - memory allocatable

This metric measures the total allocatable memory. The most detailed level of aggregation is node. The value corresponds to the allocatable memory of a node.

Kubernetes: Container - Working set memory (by node)

This metric measures the current working set memory (memory that cannot be reclaimed under pressure) by container. The OOM Killer is invoked if the working set exceeds the limit. The most detailed level of aggregation is node.

Kubernetes: Pod count (by node)

This metric measures the number of pods. The most detailed level of aggregation is node. The value corresponds to the count of all pods.

Kubernetes: Node - pod allocatable count

This metric measures the total number of allocatable pods. The most detailed level of aggregation is node. The value corresponds to the allocatable pods of a node.

Kubernetes: Pod - CPU requests (by node)

This metric measures the effective cpu requests. The most detailed level of aggregation is node. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Pod - memory requests (by node)

This metric measures the effective memory requests. The most detailed level of aggregation is node. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Resource quota - CPU limits

This metric measures the cpu limit quota. The most detailed level of aggregation is resource quota. The value corresponds to the cpu limits of a resource quota.

Kubernetes: Resource quota - CPU limits used

This metric measures the used cpu limit quota. The most detailed level of aggregation is resource quota. The value corresponds to the used cpu limits of a resource quota.

Kubernetes: Resource quota - memory limits

This metric measures the memory limit quota. The most detailed level of aggregation is resource quota. The value corresponds to the memory limits of a resource quota.

Kubernetes: Resource quota - memory limits used

This metric measures the used memory limits quota. The most detailed level of aggregation is resource quota. The value corresponds to the used memory limits of a resource quota.

Kubernetes: Resource quota - pod count

This metric measures the pods quota. The most detailed level of aggregation is resource quota. The value corresponds to the pods of a resource quota.

Kubernetes: Resource quota - pod used count

This metric measures the used pods quota. The most detailed level of aggregation is resource quota. The value corresponds to the used pods of a resource quota.

Kubernetes: Resource quota - CPU requests

This metric measures the cpu requests quota. The most detailed level of aggregation is resource quota. The value corresponds to the cpu requests of a resource quota.

Kubernetes: Resource quota - CPU requests used

This metric measures the used cpu requests quota. The most detailed level of aggregation is resource quota. The value corresponds to the used cpu requests of a resource quota.

Kubernetes: Resource quota - memory requests

This metric measures the memory requests quota. The most detailed level of aggregation is resource quota. The value corresponds to the memory requests of a resource quota.

Kubernetes: Resource quota - memory requests used

This metric measures the used memory requests quota. The most detailed level of aggregation is resource quota. The value corresponds to the used memory requests of a resource quota.

Kubernetes: Workload conditions

This metric describes the status of a Kubernetes workload. The most detailed level of aggregation is workload.

Kubernetes: Pod - desired container count

This metric measures the number of desired containers. The most detailed level of aggregation is workload. The value is the count of all containers in the pod's specification.

Kubernetes: Container - CPU throttled (by workload)

This metric measures the total CPU throttling by container. The most detailed level of aggregation is workload.

Kubernetes: Container - CPU usage (by workload)

This metric measures the total CPU consumed (user usage + system usage) by container. The most detailed level of aggregation is workload.

Kubernetes: Pod - CPU limits (by workload)

This metric measures the effective cpu limits. The most detailed level of aggregation is workload. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Pod - memory limits (by workload)

This metric measures the effective memory limits. The most detailed level of aggregation is workload. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

[Deprecated] Kubernetes: Container - Memory RSS (by workload)

This metric measures the true resident set size (RSS) by container. RSS is the amount of physical memory used by the container's cgroup - either total_rss + total_mapped_file (cgroup v1) or anon + file_mapped (cgroup v2). The most detailed level of aggregation is workload. Deprecated - use builtin:kubernetes.workload.memory_working_set instead.

Kubernetes: Container - Working set memory (by workload)

This metric measures the current working set memory (memory that cannot be reclaimed under pressure) by container. The OOM Killer is invoked if the working set exceeds the limit. The most detailed level of aggregation is workload.

Kubernetes: Workload - desired pod count

This metric measures the number of desired pods. The most detailed level of aggregation is workload. The value corresponds to the 'replicas' defined in a deployment resource and to the 'desiredNumberScheduled' for a daemon set resource's status as example.

Kubernetes: Pod - CPU requests (by workload)

This metric measures the effective cpu requests. The most detailed level of aggregation is workload. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Pod - memory requests (by workload)

This metric measures the effective memory requests. The most detailed level of aggregation is workload. The pod's effective request/limit for a resource is the higher of the sum of all app containers request/limit for a resource and the effective init request/limit for a resource.

Kubernetes: Container count

This metric measures the number of containers. The most detailed level of aggregation is workload. The metric counts the number of all containers.

Kubernetes: Event count

This metric counts Kubernetes events. The most detailed level of aggregation is the event reason. The value corresponds to the count of events returned by the Kubernetes events endpoint. This metric depends on Kubernetes event monitoring. It will not show any datapoints for the period in which event monitoring is deactivated.

Kubernetes: Node count

This metric measures the number of nodes. The most detailed level of aggregation is cluster. The value is the count of all nodes.

Kubernetes: Pod count (by workload)

This metric measures the number of pods. The most detailed level of aggregation is workload. The value corresponds to the count of all pods.

Kubernetes: Workload count

This metric measures the number of workloads. The most detailed level of aggregation is namespace. The value corresponds to the count of all workloads.

Process availability %

This metric provides the percentage of time when a process is available. It is sent once per minute with a 10-second granularity - six samples are aggregated every minute. If the process is available for a whole minute, the value is 100%. A 0% value indicates that it is not running. It has a "Process" dimension (dt.entity.process_group_instance).

Process traffic in

This metric provides size of incoming traffic of a process. It helps to identify processes generating high network traffic on a host. The result is expressed in kilobytes. It has a "PID" (process.pid), "Parent PID" (process.parent_pid), "process owner" (process.owner), "process executable name" (process.executable.name), "process executable path" (process.executable.path), "process command line" (process.command_line) and "Process group instance" (dt.entity.process_group_instance) dimensionsYou can learn more about the Process instance snapshot at https://dt-url.net/process-instance-snapshots-doc.

Process traffic out

This metric provides size of outgoing traffic of a process. It helps to identify processes generating high network traffic on a host. The result is expressed in kilobytes. It has a "PID" (process.pid), "Parent PID" (process.parent_pid), "process owner" (process.owner), "process executable name" (process.executable.name), "process executable path" (process.executable.path), "process command line" (process.command_line) and "Process group instance" (dt.entity.process_group_instance) dimensionsYou can learn more about the Process instance snapshot at https://dt-url.net/process-instance-snapshots-doc.

Process average CPU

This metric provides the percentage of the CPU usage of a process. The metric value is the sum of CPU time every process worker uses divided by the total available CPU time. The result is expressed in percentage. A value of 100% indicates that the process uses all available CPU resources of the host. It has a "PID" (process.pid), "Parent PID" (process.parent_pid), "process owner" (process.owner), "process executable name" (process.executable.name), "process executable path" (process.executable.path), "process command line" (process.command_line) and "Process group instance" (dt.entity.process_group_instance) dimensionsYou can learn more about the Process instance snapshot at https://dt-url.net/process-instance-snapshots-doc.

Process memory

This metric provides the memory usage of a process. It helps to identify processes with high memory resource consumption and memory leaks. The result is expressed in bytes. It has a "PID" (process.pid), "Parent PID" (process.parent_pid), "process owner" (process.owner), "process executable name" (process.executable.name), "process executable path" (process.executable.path), "process command line" (process.command_line) and "Process group instance" (dt.entity.process_group_instance) dimensionsYou can learn more about the Process instance snapshot at https://dt-url.net/process-instance-snapshots-doc.

Incoming messages

The number of incoming messages on the queue or topic

Outgoing messages

The number of outgoing messages from the queue or topic

New attacks

Number of attacks that were recently created. The metric supports the management zone selector.

New Muted Security Problems (global)

Number of vulnerabilities that were recently muted. The metric value is independent of any configured management zone (and thus global).

New Open Security Problems (global)

Number of vulnerabilities that were recently created. The metric value is independent of any configured management zone (and thus global).

New Open Security Problems (split by Management Zone)

Number of vulnerabilities that were recently created. The metric value is split by management zone.

Open Security Problems (global)

Number of currently open vulnerabilities seen within the last minute. The metric value is independent of any configured management zone (and thus global).

Open Security Problems (split by Management Zone)

Number of currently open vulnerabilities seen within the last minute. The metric value is split by management zone.

New Resolved Security Problems (global)

Number of vulnerabilities that were recently resolved. The metric value is independent of any configured management zone (and thus global).

Vulnerabilities - affected process groups count (global)

Total number of unique affected process groups across all open vulnerabilities per technology. The metric value is independent of any configured management zone (and thus global).

Vulnerabilities - affected not-muted process groups count (global)

Total number of unique affected process groups across all open, unmuted vulnerabilities per technology. The metric value is independent of any configured management zone (and thus global).

Vulnerabilities - affected entities count

Total number of unique affected entities across all open vulnerabilities. The metric supports the management zone selector.

CPU time

CPU time consumed by a key request within a particular request type. Request types classify requests, e.g. Resource requests for static assets like CSS or JS files. For detailed information on how service timings are calculated, https://dt-url.net/service-timings.