Synthetic Monitoring page data

Synthetic Monitoring page data dimensions

Account (id: gomezAccount)

Name of the Dynatrace Performance Network account.

Application (id: bgAppl)

A universal container that can accommodate transactions.

Backbone node (id: gomezSite)

Name of the Dynatrace Performance Network node.

Business day (id: businessDay)

The classification of days as business or non-business, as defined in the Business Hours Configuration tool.

Business hour (id: businessHour)

The classification of hours, as business and non-business, as defined in the Business Hours Configuration tool. Possible values are Business and Off-business .

Client area (id: cLocArea)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client city (id: cGeoCity)

Geographical data about the client site, or the Backbone node in case of Synthetic Backbone reports.

Client country (id: cGeoCountry)

Geographical data about the client country, or the Backbone node country in case of Synthetic Backbone reports.

Client geographical region (id: cGeoRegion)

Geographical data about the client region, or the Backbone node region in case of Synthetic Backbone reports..

Client group (id: userNGr)

The client's group, or a group of Backbone nodes in case of Synthetic Backbone reports, as manually defined in Central Analysis Server.

Client IP address (id: cIP)

The IP address of the client, or the Backbone node in case of Internet synthetic reports.

Client region (id: cRegion)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbone nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client site (id: cLoc)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions, clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client site AS number (id: ASNum)

Client site's Autonomous System Number (ASN).

Client site description (id: cLocDescr)

The optional description of the client site, or a Backbobne node in case of Synthetic Backbone reports.

Client site ID (id: cLocDnsName)

In cases when sites are ASes, Client Site ID contains the AS number, which is also given in Client ASN, or Backbone node ASN in case of Synthetic Backbone reports. For manual sites, Client Site ID is identical to Client site, and contains the site name as defined in your site configuration. Sites based on CIDR blocks or subnets are identified by IP addresses.

Client site IP address (id: LocIP)

The client site IP address.

Client site type (id: cLocType)

One of site types: AS, Active, CIDR Block, Default, External, Manual, Network or Predefined. External is a site defined by a user in external configuration files. Manual site is defined by a user by means of configuration interface on the report server. Predefined sites are based on a mapping contained in a special configuration file.

Client site type ID (id: cLocTypeId)

Client site type ID

Client site UDL (id: clientLocUdl)

A dimension designed to filter only the User Defined Links. By default it is set to true (Yes) for WAN Optimization Sites report.

Client site WAN Optimized Link (id: clientLocWanOpt)

Indicates whether a site to which the client belongs is selected as both a UDL and a WAN optimized link.

Country (id: gomezCountry)

Name of the country where the Peer Population is located. Private Last Mile peer population definition category.

Data source (id: dataProd)

The name of the data source in case you have configured a number of associated report servers to be used as data sources on the DMI screen.

Day of the week (id: dayOfWeek)

The textual representation of the day of the week.

Hour of the day (id: hrD)

The numerical representation of the hour of the day, that is, numbers from 0 to 23.

ISP (id: gomezGeoIsp)

Internet Service Provider used to execute the Dynatrace Performance Network test.

Location ID (id: locID)

Location ID

Machine name (id: gomezMachineName)

Name or ID of the machine, and the IP preference (IPv4, IPv6, or both) for the machine. Private Last Mile peer population definition category.

Page (id: gomezStep)

The page name accessed within a test.

Page sequence number (id: gomezStepSeqNum)

Sequence number of the page.

Peer group (id: gomezPeerGroup)

A number of specific machines grouped into a population to identify the impact of geographic configurations, ISP, or any other criteria in determining the Dynatrace Network Test performance.

Region (id: gomezGeoRegion)

Geographical region (state/province) from where the Dynatrace Performance Network test was executed.

Test (id: gomezTest)

Name of the Dynatrace Performance Network test.

Test time (id: gomezTTs)

The exact time of the test execution.

Test type (id: gomezTestType)

The type of the Dynatrace Performance Network test. Last Mile, Private Last Mile or Backbone.

Time (id: begT)

The time stamp of the data presented on the report.

Transaction (id: bgTrans)

A universal container that can accommodate operations. This metric refers only to transactions without errors.

Transaction step (id: bgBussStep)

The step as configured in a transaction definition. Step configuration is built on DCRUM data using operations, tasks, modules or services. Steps are contained within transactions and carry the entire transaction configuration.

Transaction step sequence number (id: bgBussStepSeqNum)

The sequence number of a step is used for presentation purposes. It marks the order of a particular step in a transaction configuration. You can order steps within each transaction if such an ordering makes sense for the overall monitored application paradigm. The transaction step sequence does not affect data aggregation.

User defined field 1 (id: gomezUserDefField1)

If custom fields were defined when Private Last Mile was installed, value for the first custom field. Private Last Mile peer population definition category. The recommended value is the City where the Private Last Mile installation is located

User defined field 2 (id: gomezUserDefField2)

If custom fields were defined when Private Last Mile was installed, value for the second custom field. Private Last Mile peer population definition category. The recommended value is the Partner name.

User defined field 3 (id: gomezUserDefField3)

If custom fields were defined when Private Last Mile was installed, value for the third custom field. Private Last Mile peer population definition category. The recommended value is the functional role.

User group (id: userGr)

The name of the users group.

Synthetic Monitoring page data metrics

1st byte time

Time between the completion of the TCP connection with the destination server that will provide the displayed page's HTML, graphic, or other component and the reception of the First Packet (also known as first byte) for that object. Overloaded web servers often have a long First Byte time.

Application performance

For transactional protocols, this is the percentage of software service operations completed in a time shorter than the performance threshold. For SMTP and transactionless TCP-based protocols, this is the percentage of monitoring intervals in which user wait time per kB of data was shorter than the threshold value.

Byte limit exceeded errors

The number of byte Limit errors. The byte limit error occurs when the attempt to download a page or object was blocked because the reported size of the object was greater than the current limit.

Bytes (average)

The average number of bytes downloaded for the pages per test.

Bytes (sum)

The total number of bytes downloaded for pages.

Connections (average)

The average number of connections established for pages per test.

Connections (sum)

Total number of connections established for pages.

Connect time

The time (in seconds) that it takes to connect to a Web server across a network. After obtaining the target IP address by using the DNS Lookup, the Dyntrace Performance Network Agent establishes a TCP connection with the device at that IP address. TCP connections are started by the agent's transmitting a special "SYN" packet and then receiving an "ACK" packet from the server. The elapsed time between transmitting the SYN to the server and receiving the ACK response is the Initial Connection time.

Content match errors

The number of errors caused by the content not matching the condition defined for the page or object.

Content time

Time required to receive the content of a page or page component starting with the receipt of the first content and ending with the last packet received.

DNS time

The time it takes to translate the host name (for example, www.gomez.com) into the IP address (for example, 208.159.60.20). The Dyntrace Performance Network Agent performs this translation by using the Internet's standard Domain Name Service (DNS).

Hosts (average)

The average number of hosts associated with the page.

Hosts (sum)

Total number of hosts associated with the page(s).

HTTP client errors

The number of HTTP client errors.

HTTP server errors

The number of HTTP server errors.

Number of 200 objects

The total number of page objects with a return code of 200-299.

Number of 300 objects

The total number of page objects with a return code of 300-399.

Number of 400 objects

The total number of page objects with a return code of 400-499.

Number of 500 objects

The total number of page objects with a return code of 500-599.

Objects (average)

The average number of objects downloaded per page.

Objects (sum)

The total number of downloaded page objects.

Objects breakdown

The breakdown into successful and failing objects.

Objects with network errors

The total number of page objects with network related errors.

Objects with server errors

The total number of page objects with server related errors.

Page availability

The percentage of successful pages vs all pages.

Page error breakdown

The breakdown of page errors, that is Socket time-out errors, Byte limit exceeded errors, User script errors, and Content match failures.

Page response time

The average time it took the page to produce a response for the given request.

Pages executed

The number of pages tested.

Pages executed (failed)

The number of tested pages reported as failed.

Pages executed (fast)

The number of tested pages reported as fast.

Pages executed (slow)

The number of tested pages reported as slow.

Pages executed breakdown

Breakdown into failed, slow and fast tested pages.

Page time breakdown

The breakdown of components, that is DNS time, connect time, SSL time, 1st byte time, content time, of page load for all object associated with the page.

Percentage of pages executed (slow)

The percentage of tested pages reported as slow.

Processing time

The average client-side processing time.

Slow pages threshold (max)

The threshold above which the page is reported as fast.

Slow pages threshold (min)

The threshold below which the page is reported as failed.

Socket time-out errors

The number of errors caused by no response to the attempts to open a TCP connection to the server.

SSL time

Time it takes to establish a Secure Socket Layer (SSL) connection and exchange SSL keys.

User script errors

The number user script errors. The user script error occurs when JavaScript on the page did not or was not able to execute properly.

W3C connect time

Connect time is the time elapsed from just before the browser connects to the server until the connection to the server is established.

W3C DNS time

DNS Lookup time is the time elapsed from immediately before the DNS lookup for the domain occurs until the time immediately after the DNS lookup occurs.

W3C dom complete time

DOM Complete time is the time elapsed from when the prompt to unload the previous document occurs until the time immediately before the document.readyState is set to complete.

W3C dom interactive time

DOM Interactive time is the time elapsed from immediately after the prompt to unload the previous document occurs until the time immediately before the document.readyState is set to interactive.

W3C fetch time

Fetch time is the time elapsed from immediately before the check for any relevant application caches (if HTTP GET or an equivalent is used) or the time when the resource is fetched until immediately before the DNS lookup occurs.

W3C first paint time

Time to First Paint represents the time when the document began to be displayed or 0 if the document could not be loaded. This metric is only supported for IE Browser Agent. This metric has not been integrated by either Chrome or Firefox into their browser technologies.

W3C load time

Load time is the time elapsed from when the load event of the current document completes until the time immediately before the load event of the current document is fired.

W3C redirect time

Redirect time is the time elapsed from the start time of a URL fetch that initiates a redirect until the time after the last byte of the last redirect response is received.

W3C request time

Request time is the time elapsed from when the browser sends the request for the URL until the time just after the browser receives the first byte of the response.

W3C response time

Response time is the time elapsed from the time immediately after the user agent receives the first byte of the response from the server until the time immediately after the user agent receives the last byte of the current document or immediately before the transport connection is closed, whichever comes first.

W3C SSL time

SSL time is the time elapsed from just before the browser connects to the server and starts the handshake process to secure the current connection until the connection to the server is established.

W3C total page load time

Total Page Load Time is the time elapsed from immediately after the prompt to unload the previous document occurs until the load of the current document ends

W3C unload time

Unload time is the time elapsed from immediately before the start of the unload of the previous document until the time immediately after the unload finishes.