Synthetic Monitoring test data

Synthetic Monitoring test data dimensions

Account (id: gomezAccount)

Name of the Dynatrace Performance Network account.

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.

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.

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 test data metrics

Bytes downloaded

The total number of downloaded bytes.

Bytes downloaded per test

The average number of bytes downloaded per test.

Failing objects

The number of failing page objects within the tests.

Failing pages

The number of unsuccessful attempts to access a page within a test.

Number of objects

The number of tested page objects, including successful and failing objects.

Number of pages

The number of tested pages.

Number of tests

The number of test executions.

Objects breakdown

The breakdown into successful and failed page objects, accompanied by the number of all objects.

Pages breakdown

The breakdown into successful and failed pages, accompanied by the number of all pages.

Pages tested per test

The average number of tested pages, including successful and failed attempts, per test.

Percentage of failed objects

The percentage of failed page objects vs all objects.

Percentage of failed pages

The percentage of failed pages vs all pages.

Percentage of successful objects

The percentage of successfully downloaded page objects vs all objects.

Percentage of successful pages

The percentage of successfully accessed pages vs all pages.

Response time

Total time required to download a complete web page and its objects. For full object tests, response time is the time, as measured in seconds, from when a user clicks on a link to the time that the Web page is fully downloaded. For HTML-only tests, it is the time, as measured in seconds, from when a user clicks on the link to the time when the root object is downloaded. Response time encompasses the collection of all objects that make up a page including third-party content on off-site servers, graphics, frames, redirections, and so on. For an operation flow (a series of interactive operations on several web pages), the response time is measured from the start of the operational flow (the moment a user clicks on a link) to the end of the operational flow (the content from the last web page content is downloaded.)

Successful objects

The number of successfully tested page objects.

Successful pages

The number of successful attempts to access a page within a test.

Test availability

The percentage of successful tests vs all tests.