stillattack.blogg.se - Solr jvm memory monitor

Server contribution - load action (by key user action, user type) īuiltin:apps.

Response end - XHR action (by key user action, browser) īuiltin:apps. Response end - load action (by key user action, browser) īuiltin:apps. Network contribution - XHR action (by key user action, user type) īuiltin:apps. Network contribution - load action (by key user action, user type) īuiltin:apps. Load event start - load action (by key user action, browser) īuiltin:apps. Load event end - load action (by key user action, browser) īuiltin:apps. Largest Contentful Paint - load action (by key user action, browser) īuiltin:apps.

Largest Contentful Paint - load action (by key user action, geolocation, user type) īuiltin:apps. Largest Contentful Paint - load action (by key user action, user type) īuiltin:apps. browserįirst Input Delay - load action (by key user action, browser) īuiltin:apps. geoįirst Input Delay - load action (by key user action, geolocation, user type) īuiltin:apps. userTypeįirst Input Delay - load action (by key user action, user type) īuiltin:apps. Time to first byte - XHR action (by key user action, browser) īuiltin:apps. Time to first byte - load action (by key user action, browser) īuiltin:apps. browserĪction duration - XHR action (by key user action, browser) īuiltin:apps. browserĪction duration - load action (by key user action, browser) īuiltin:apps.

browserĪction duration - custom action (by key user action, browser) īuiltin:apps. browserĭOM interactive - load action (by key user action, browser) īuiltin:apps. browserĬumulative Layout Shift - load action (by key user action, browser) īuiltin:apps. geoĬumulative Layout Shift - load action (by key user action, geolocation, user type) īuiltin:apps. userTypeĬumulative Layout Shift - load action (by key user action, user type) Īuto avg count max median min percentile sumīuiltin:apps. browserĪction count - XHR action (by key user action, browser) īuiltin:apps. browserĪction count - load action (by key user action, browser) īuiltin:apps. browserĪction count - custom action (by key user action, browser) īuiltin:apps. User action rate - affected by JavaScript errors (by key user action, user type) īuiltin:apps. Note: For the purposes of calculating monitoring consumption, collecting the same custom metric for two hosts counts as two separate custom metrics. Collecting the same metric for two individual hosts results in two timeseries of the same custom metric type, as shown in the example below: Each component’s custom metric results in a separate timeseries.įor example, if you define a new custom metric called Files count that counts the newly created files within a directory, this new metric can be collected either for one host or for two individual hosts. Following the definition of a custom metric, the metric can be reported for multiple monitored components. Custom metrics are sent to Dynatrace through various interfaces. The semantics of custom metrics are defined by you and aren't included in the default OneAgent installation. Certain built-in metrics are disabled by default and, if turned on, will consume DDUs.These metrics cover a wide range of supported technologies, including Apache Tomcat, NGINX, Couchbase, RabbitMQ, Cassandra, Jetty, and many others.Ī custom metric is a new type of metric that offers a user-provided metric identifier and unit of measure.

Omit the parameter to obtain all the metrics of your environment.Ĭustom metrics are defined or installed by the user, while built-in metrics are by default part of the product.

metricSelector=calc:*-to obtain all calculated metrics.

metricSelector=ext:*-to obtain all metrics coming from extensions.

Depending on which metrics you want to query, one of the following values for the metricSelector parameter:.

fields=displayName,unit,aggregationTypes,dduBillable-to obtain the same set of fields as you see in these tables.

pageSize=500-to obtain the largest possible number of metrics in one response.

We recommend the following query parameters: To view all the metrics available in your environment, use the GET metrics API call. Metrics that are based on extensions (prefix ext:) and calculated metrics (prefix calc:) are custom metrics, not built-in metrics DDU consumption for these metrics can vary widely depending on how you use Dynatrace. Built-in metrics are included in the product out of the box, in some cases as part of built-in extensions.įrom a licensing perspective, the metrics in the table below come either via OneAgent monitoring, and are therefore part of the host unit license, or they come as part of Digital Experience Monitoring and are covered by DEM units. Each Dynatrace-supported technology offers multiple "built-in" metrics.