Endpoint Agents can run two types of Scheduled Tests at regular intervals. The two tests are similar to the Network Layer's Agent to Server test type, and to the Web Layer's HTTP Server test type run by a Cloud or Enterprise Agent.
Table of contents
- Using the HTTP Server test view
- Using the Network test view
- Data filtering
- Frequently asked questions
Scheduled Test views are nested under Endpoint Agents > Views. Once there, select Scheduled Tests under the Views:
The following figure shows the default Endpoint scheduled test results view, with an HTTP Server test selected:
The Endpoint Agent scheduled test results view consists of the following components:
- Test selector: Selects the test to display in the view
- Layer selector: Selects the layer to display. The HTTP Server tests have Network layer available when Perform network measurements setting is enabled in test's Advanced Settings tab.
- Data filters: Filters that can be applied to displayed data. The data displayed in the time slide (5, 6) and data view (10) is affected.
- Metric selector: Choice defines the metric to be displayed on the time slide (5).
- Colored line on timeline: Time series visualization of the selected metric (4)
- Grey area on timeline: Time series of the number of endpoint agents providing the data
- Time interval selector: Data from the selected time interval is displayed in the data view (10) below.
- Time range selector: Colored section defines the displayed data (5,6). The remaining data is shown in grey.
- Selected time: Confirmation of the selected time interval
- Data view pane for the selected time interval: Display of data submitted by the endpoint agents that match the configured filters (3) in the selected time interval (7, 9).
In Figure 3 above, the HTTP Server test results view is depicted. The HTTP Server test collects the following metrics:
- Availability: Percentage of time that the site is available, aggregated across all displayed agents.
- Response time: Also known as time-to-first-byte, this is the time elapsed from the beginning of the request (before DNS request) until the client receives the first byte of the response from the server.
- Throughput: The metric is calculated by dividing the total wire size by the receive time and expressed in MB/s.
The bottom pane on the HTTP Server view is split into two tabs:
- Map view shows the geolocation of the agents in a map and a break down of the connection status by different phases. The informational message below the status bars shows the number of agents that collected data out of the total checked-in agents for the selected test time interval.
- Table view provides a break down of the selected metrics collected per agent for the selected time interval.
The Network layer can be opened by clicking on the Network link (1) as shown below:
Click on the Network link as outlined in the screen capture above leads to the Network test results view. The Network (Agent to Server) test on an Endpoint agent measures the following metrics (2):
- Loss: End-to-end packet loss. The percentage of packets lost is calculated by subtracting the number of reply packets the agent receives from the target (responses) from the number of packets sent by the agent, then dividing by the number of packets sent, then multiplying by 100.
- Latency: The average of the round-trip packet time. Round-trip packet time is the time from which a packet is sent by the agent to the time the agent receives a reply.
- Jitter: The standard deviation of latency. The standard deviation indicates how widely spread are the measurements around the average. A larger standard deviation indicates a wider spread of the measurements.
The available metrics can be selected for display in the Metrics drop-down menu (pointer #2 in the Screen capture no.4 above). Additionally, metrics are also represented and clickable (2) on the left side of the Map (1) tab content on the bottom pane:
The bottom pane on the Network view is broken down into three tabs:
- Path Visualization (outlined in the screen capture no.6 below) shows an L3 hop by hop topology view from the source endpoint agent to the test target.
- Map view (outlined above in the screen capture no.5) shows the geolocation of the agents in a map view (4) and the collected metrics (3). The informational messages above (2) and below (4) below the metrics bars show the number of agents that collected data out of the total checked-in agents for the selected test time interval.
- Table view provides a break down of the metrics collected per agent for the selected time interval.
Sample Path Visualization view for network tests:
More information of the Path Visualization view is available in the Using the Path Visualization View article.
Endpoint Agent views provide extensive data filtering capabilities that enable users to drill down the data and present it in the most useful manner. In the following figure, the filtering controls are indicated:
Available filtering controls:
- Configured filters: Shows currently configured filters. Clicking the X icon removes the corresponding filter.
- New filter dialogue: Applies a new filter to the data shown. Multiple filters can be configured. Filters are combined using the logical operator "AND".
- Available filters: Showing the list of filters available.
- Path Visualization-specific configured filters: Shows currently configured filters (path visualization only). Clicking the X icon removes the corresponding filter.
- Path Visualization-specific new filter dialogue: Applies a new filter to the data shown (path visualization only). Multiple filters can be configured. Filters are combined using the logical operator "AND".
- Apply to the entire view: If a filter set configured specifically for the path visualization seems useful, clicking this link will apply the same filter to the entire view - the filters will be copied into the configured filters section at the top of the view (1).
A dedicated section containing questions and answers about scheduled tests on Endpoint Agents is available in the Creating scheduled tests on Endpoint Agents article.