View Stream Details
Streams Overview
At the time of Test or Monitor creation, you can configure evaluation criteria for various metrics.
When you run a Test or a Monitor, Paragon Automation instructs the Test Agents to send or receive traffic in the network by using the selected protocols. Each measurement produces one or more Stream of metrics.
The Test and Monitor evaluate these Streams and present a summary in the respective Stream-Name Details pages. On violation of a configured evaluation criterion, an event is generated. You can view the Stream graphs on Stream-Name Details page and identify the cause of violation.
Access Stream-Name Details Page
To access the Stream-Name Details page:
Select Observability > Active Assurance > Tests or Observability > Active Assurance > Monitors, and click a Test-Name or a Monitor-Name.
The Test-Name or Monitor-Name page appears.
Click a Stream-Name from the Streams table.
The Stream-Name Details page appears.
Tasks You Can Perform
On the Stream-Name Details page, you can:
-
View Stream results for a specific period—You can select a predefined period (15m, 2h, 4h, 8h, 16h, 24h, 1w) for which you want to view the results of all Streams. You can also click Custom to set a custom time range for which you want to view the results of all Streams. When the Custom Time Range selection page appears, specify the day and time in the From and To fields, respectively.
-
View the list of events—You can view the events generated by the Streams, and the date and time at which the event has occurred. The Event bar displays events based on the severity levels. The high-priority event, Critical, is displayed at the top of the events list, while the low-priority event, Information, is displayed at the end of the list.
To view the list of all the events generated in the order of occurrence, click the More option. When you click More, the Events page appear. You can also sort the columns in the Events page. For more information on the events generated by the Streams, see Table 1.
-
View the events on an event bar—You can view all the events generated on an event bar. The event bar is a color-driven bar graph that indicates events and the time at which the event has occurred. The colors represent the severity of events. That is, critical events are represented in red, errors are represented in orange, warnings are represented in yellow, information is represented in blue.
You can also hover over an event generated on the event bar to view the start time, end time, total number of events generated, and the number of events generated in each type.
-
View the status of the selected Stream—You can view the status of the selected Stream. The Stream is displayed as an event bar. Click > to view the event bar for the Stream. When you hover over the event bar, you can view the events generated for the Stream.
-
View the configurations details—You can view all the parameters you specified for a Task when you created a Test or a Monitor. Click Config to view all the parameters you have configured. For more information, see Create a Test and Create a Monitor.
-
View the stream graph for a specific metric—You can view a stream graph of a specific metric. To view a stream graph, enable the Metric-Name toggle button for which you want to view the stream graph. The Metric-Name can vary based on the Tasks you have selected. A list of all the metrics are defined in Table 2.
-
View stream graphs for all metrics—You can view the stream graphs of all the metrics. To display stream graphs of all the generated metrics, click the Show All button.
-
Group stream graphs by metrics—You can organize the stream graphs logically to get a coherent view of metrics.
When you enable the Group Metrics toggle button, the metrics are logically categorized. That is, all the related metrics are grouped under a primary stream graph. For example, for a ping Task, metrics such as minimum time response, maximum time response, and average time responses will be grouped under Response (primary metric).
Once enabled, you can select and deselect the individual metrics in an stream graph. The data related to the metrics you selected will be displayed on the stream graph.
When you disable the Group Metrics toggle button, all the metrics are displayed. By default, this toggle button is disabled.
-
View stream graphs in compact view—You can view all the stream graphs in compact mode to navigate easily between individual graphs. The compact view provides a streamline view of multiple graphs. To view the stream graphs in compact mode, enable the Compact view toggle button.
All the stream graphs for the metrics you toggled on will be displayed in compact view. The compact view provides a concise display of all the stream graphs that helps you to analyze various metrics simultaneously.
Field | Description |
---|---|
Severity |
The type of severity level of the event that is raised when there is a criteria violation. The following are the severity levels: Critical—Indicates that the event is critical and needs immediate attention. Warning—Indicates that the event needs to be fixed but does not require immediate attention. Info—Indicates that an event is raised that provides information on progress of the Task and does not require attention. Error—Indicates that the event needs to be fixed and requires immediate attention and troubleshooting. |
Description |
The description that you specified when you configured the evaluation criteria for a Monitor. |
Raise Time |
The date and time when the event was generated. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM. The date and time is displayed according to the Raise delay you specified when you configured the evaluation criteria for a Monitor. For example, Mar 5, 2024, 4:29:52 PM. |
Clear Time |
The date and time when the event was cleared. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM. The date and time is displayed according to the clear delay you specified when you configured the evaluation criteria for a Monitor. For example, Mar 5, 2024, 4:29:52 PM. |
Subject |
The details of the event generated is displayed in JSON format. It displays various IDs related to the event like Test Agent ID, Monitor ID, Task ID, Stream ID, and so on. To view the details, click show hyperlink. |
Data |
The details of the evaluation criteria associated with the event generated. To view data, click show hyperlink. |
Stream Metric | Description |
---|---|
DNS |
|
Minimum response time |
Minimum response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
Average response time |
Average response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
Maximum response time |
Maximum response time of all the requests in the result interval. Response time is the time elapsed from when the DNS request was sent until a response was received. The response time is calculated in milliseconds. |
ES timeout |
ES timeout is the errored-seconds raised when Test Agent considers a DNS request to be timed-out. The ES timeout is calculated in milliseconds. |
ES lifetime |
ES lifetime is the errored-seconds raised when Test Agent fails the DNS request as there is no response received within the specified Request lifetime. The ES lifetime is calculated in milliseconds. |
ES response |
ES response is the errored-seconds raised when the DNS Response code differs from the expected response code or when the response differs from the expected response. |
ES |
ES is the number of seconds during which error second thresholds are violated. It is the total number of error-seconds raised during result interval. The ES is calculated in milliseconds. |
HTTP |
|
Connect time |
Connect time is the time taken to set up a TCP connection between Test Agent and the Web server by using a TCP handshake. The connect time is calculated in milliseconds. |
First byte received |
First byte received indicates the total time taken by Test Agent to receive the first byte of response packet from the Web server. The first byte received time is calculated in milliseconds. |
Minimum response time |
Minimum response time is the duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
Average response time |
Average response time is the average duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
Maximum response time |
Maximum response time is the maximum duration when the request was sent until the full response is received. TCP connection setup time is included in the average response duration. The response time is calculated in milliseconds. |
Size |
Size indicates the total size of the data transferred from a remote endpoint to Test agent in response to an HTTP request. The size also includes the header size. The size is calculated kilobytes. |
Rate |
Rate is the download rate at which the response is received from first byte to last. The rate is displayed in Megabits Per Second. |
ES timeout |
ES timeout is the number of errored-seconds raised because no HTTP response was received before the timeout period expires. The ES timeout is calculated in milliseconds. |
ES response |
ES response is the errored-seconds raised when the response code differs from the expected response code or when the response content differs from the expected response. |
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised during the result interval. The ES is calculated in milliseconds. |
Ping |
|
Successful ping counts |
Number of ICMP or UDP echo request which has received a response during the result interval. The higher ping counts denote to a more reliable the network connection. |
Minimum round-trip delay |
Minimum round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the device. The delay is calculated in milliseconds. |
Maximum round-trip delay |
Maximum round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the remote endpoint. The delay is calculated in milliseconds. |
Average round-trip delay |
Average round-trip delay of all the requests in the result interval. Round-trip measures the duration from the time Test Agent sends a request until it receives a response from the remote endpoint. The delay is calculated in milliseconds. |
Average round-trip DV |
Average round-trip delay variance in the result interval. Round-trip delay variance is the difference in time between the request with longest round-trip time and the shortest round-trip time. The delay variance is calculated in milliseconds. |
Lost |
Indicates the number of ping request packets sent by Test Agent that did not receive a response before the configured lifetime. |
Loss |
Indicates the number of ping request packets sent by Test Agent that did not receive a response before the configured lifetime. |
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised during the result interval. The ES is calculated in milliseconds. |
ES loss |
ES loss is the number of errored-seconds during the result interval where a request or more did not receive a response. The ES loss is calculated in milliseconds. |
ES delay |
ES delay is the number of errored-seconds raised when Test Agents experience round-trip delay greater than the configured timeout. The ES delay is calculated in milliseconds. |
ES response |
ES response is the number errored-seconds raised because Test Agent failed to resolve the destination hostname or because the response payload does not match what was sent. |
ES delay variance (DV) |
ES delay variance is the number of errored-seconds raised because Test Agent measures a variance in delay greater than the configured delay variation threshold. The ES delay variance is calculated in milliseconds. |
IPTV MPEG |
|
Rate |
Rate indicates the bit rate of the MPEG program stream. The rate is displayed in Megabits Per Second. |
Transport rate |
Transport rate indicates the bit rate of the MPEG transport stream (MPEG-TS). It includes the overhead from the header of the Transport Stream packet. The Transport rate is displayed in Megabits Per Second. |
MPEG loss |
MPEG loss indicates the MPEG packet loss during a transmission. The loss is calculated from the continuity count (CC) errors in the MPEG stream. |
PCR jitter |
Program Clock Reference (PCR) refers to the variation in the arrival time of PCR packets when compared to the expected arrival time. The PCR jitter is displayed in milliseconds. |
PAT error |
A PAT error occurs if a Program Allocation Table (PAT) is not received on a multicast group within the configured PAT/PMT interval. |
PMT errors |
A PMT error occurs if a Program Map Table (PMT) is not received on a multicast group within the configured PAT/PMT interval. |
PID errors |
A PID error occurs if no frame is received within the specified PID interval threshold for every second that elapses. |
RTP errors |
Real-Time protocol (RTP) error indicates the number of lost packets in the RTP header. Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
RTP misordering |
RTP misorders indicates the number of misordered packets based on Real-Time protocol (RTP) header. A packet is counted as misordered if it is delivered after a packet with a higher sequence number. Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
RTP jitter |
Real-Time protocol jitter indicates the variation in the arrival time of RTP packets when compared to the expected arrival time. If the MPEG stream contains RTP header, RTP jitter is calculated by using the timestamps from the Real Time protocol (RTP). Whether an MPEG stream contains RTP headers depends on the configuration of the encoder at the head-end. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. The ES is displayed in seconds. |
ES MPEG Loss |
ES MPEG loss is the errored-seconds raised due to MPEG loss packet loss (CC errors). It is raised when the MPEG loss exceeds the configured MPEG loss threshold. |
ES Jitter |
ES jitter is the number of errored-seconds raised when the PCR jitter or RTP jitter exceeds the defined jitter threshold. |
ES invalid Stream |
ES invalid stream is an aggregate of PAT, PMT, and PID errors. If any of these types of errors are experienced in a second, an errored-second is raised. |
Netflix Speedtest |
|
Bandwidth speed |
Bandwidth speed is the speed of data transmission to the Netflix servers or from the Netflix servers. The Bandwidth speed is displayed in Megabits Per Second. |
End to End Latency |
End-to-end latency indicates the latency occurred during the transfer of data from the Test Agent to the Netflix server or vice versa. The End to End Latency is displayed in milliseconds. |
ES bandwidth |
ES bandwidth indicates the number of errored-seconds raised if the bandwidth drops below the defined value. |
ES latency |
ES latency indicates the number of errored-seconds raised if the latency exceeds the defined value. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. The ES is displayed in seconds. |
ES rate |
ES Rate is the number of errored-seconds occurred when the rate at which the UDP packet reception drops below the defined value. |
OTT - HLS |
|
Playback rate |
Playback rate indicates the actual data rate of the video stream. The rate is displayed in Megabits Per Second. |
Download rate |
Download rate indicates the download rate of the segments. When the amount of buffered data drops below the defined buffer size, the download begins. The rate is displayed in Megabits Per Second. |
Selected rate |
Selected rate indicates the data rate of the selected variant in the manifest file. The rate is displayed in Megabits Per Second. |
Buffer length |
Buffer length is the duration of the initial buffered data at a given time. When the duration of the buffered data drops below the defined value, new segments are downloaded. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. |
ES playback rate |
ES playback rate is the number of errored-seconds raised when the playback rate drops below the defined playback rate value. |
ES selected rate |
ES selected rate is the number of errored-seconds raised when selected rate drops below the defined value. |
ES download rate |
ES download rate is the number of errored-seconds raised when the download rate drops below the defined value. |
ES buffer |
ES buffer is the number of errored-seconds raised when buffer length of the video stream drops below the defined value. |
ES buffering | ES buffer is the number of errored-seconds raised when buffer length of the video stream drops below the defined value. |
TCP |
|
Rate |
Rate indicates the speed or throughput (goodput) at which the Test Agent receives the TCP packets in a selected interval of time. The rate is displayed in Megabits Per Second. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all specific ES metrics. The ES is displayed in seconds. |
ES rate |
ES Rate is the number of errored-seconds occurred when the data rate drops below the defined value. The ES rate is displayed in seconds. |
UDP |
|
Misordered packets |
Misordered packets indicates the total number of packets received by the Test Agent in a different order than they were sent. |
Rate |
Rate indicates the speed or throughput at which Test Agent receives the UDP packets in a selected interval. The rate is displayed in Megabits Per Second. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. ES is an aggregate of all the specific ES metrics. |
ES Rate |
ES Rate is the number of errored-seconds occurred when the rate at which the UDP packet reception drops below the defined value. The rate is displayed in milliseconds. |
ES Loss |
ES loss is the number of errored-seconds raised when measured packet loss exceeds the defined loss value. |
ES Delay |
ES Delay is the number of errored-seconds raised when the measured one-way delay exceeds the defined delay value. The ES delay is displayed in milliseconds. |
ES DSCP | ES DSCP is the number of errored-seconds occurred when the DSCP marked packets experience loss, delay, delay variance, or configuration issues. |
SES |
Severely errored second (SES) indicates the interval of time during which any of the defined SES thresholds were violated. |
UAS |
The Unavailable Seconds (UAS) metric indicates the number of seconds at which the service can be considered to be unavailable. |
Average delay |
Average delay indicates the average delay experienced by data packets in the UDP measurement. The average delay is displayed in milliseconds. |
Minimum delay |
Minimum delay indicates the minimum delay experienced by data packets in a UDP measurement. The minimum delay is displayed in milliseconds. |
Maximum delay |
Average delay indicates the average delay experienced by data packets in the UDP measurement. The maximum delay is displayed in milliseconds. |
Jitter |
Jitter is the difference between maximum and minimum one-way delay measured during a result interval. The jitter is displayed in milliseconds. |
Number of packets in the interval |
Number of packets in the interval. |
Percentage of packets lost |
Loss percentage indicates the percentage of packets sent from the Test Agent that were lost before reaching the receiving Test Agent. |
Lost Packet count |
Lost indicates the number of packets sent from the Test Agent that were lost before reaching the receiving Test Agent. |
TWAMP/TWAMP Light |
|
Rate |
Rate indicates the rate at which sender Test Agent receives response packets from the TWAMP reflector in a selected interval of time. The rate is calculated as the size of the response received divided by the total response time. The rate is calculated in Megabits Per Second. |
Minimum round trip time |
Minimum round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when a test packet is sent from a Test Agent until the packet is reflected back and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
Average round trip time |
Average round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when a test packet is sent from a Test Agent until the packet is reflected and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
Maximum round trip time |
Maximum round-trip delay of all the requests in the result interval. Round-trip time indicates the duration from when the test packet is sent from a Test Agent until the packet is reflected and received again on the Test Agent. Time spent in the reflector is not included. The time is calculated in milliseconds. |
Round trip time DV |
Average round-trip delay variance in result interval. Round-trip delay variance is the difference in round-trip time between the packets with the longest and the shortest round-trip time. The Round trip time DV is calculated in milliseconds. |
Received Packets |
Received packets indicates the total number of packets received by Test Agent from the reflector. |
Far-end loss |
Far-end loss indicates the percentage of packets lost between Test Agent and the Reflector. It is the percentage of packets that were lost before reaching the reflector. |
Far-end lost |
Far-end lost indicates the number of packets lost before reaching the reflector. |
Far-end misorders |
Far-end misorders indicate the number of packets sent by Test Agent that reached the reflector out of sequence compared to their original order of transmission. |
Minimum far-end delay |
Minimum one-way far-end delay indicates the minimum delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
Average far-end delay |
Average one-way far-end delay indicates the average delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
Maximum far-end delay |
Maximum one-way far-end delay indicates the average delay measured for a packet to travel from Test Agent to the Reflector. The delay is calculated in milliseconds. |
Far-end DV |
Far-end DV indicates the delay variance measured at the remote endpoint. It is the difference between the maximum and minimum one-way far-end delay. The delay is calculated in milliseconds. |
Near-end loss |
Near-end loss indicates the percentage of packets lost between the Reflector and Test Agent. It is the percentage of packets that were lost before reaching the Test Agent. |
Near-end lost |
Near-end lost indicates the number of packets lost between the Reflector and Test Agent. It is the number of packets that were lost before reaching the Test Agent. |
Near-end misorders |
Near-end misorders indicates the number of packets that reached Test Agent out of sequence compared to their original order of transmission. |
Minimum near-end delay |
Minimum one-way near-end delay indicates the minimum delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
Average near-end delay |
Average one-way near-end delay indicates the average delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
Maximum near-end delay |
Maximum one-way near-end delay indicates the maximum delay experienced by a packet to travel from the Reflector to Test Agent. The delay is calculated in milliseconds. |
Near-end DV |
Near-end DV indicates the delay variance measured at Test Agent endpoint. It is the difference between the maximum and minimum one-way near-end delay. The delay is calculated in milliseconds. |
ES |
ES is the number of seconds during which error-second thresholds were violated. It is the total number of errored-seconds raised. The ES is calculated in milliseconds. |
ES delay |
ES delay is the number of errored-seconds raised when Test Agent measures a delay greater than the configured delay threshold. The ES delay is calculated in milliseconds. |
ES loss |
ES loss is the number of errored-seconds raised when the measured loss is greater than the configured loss threshold. The ES loss is calculated in milliseconds. |
ES delay variance (DV) |
ES delay variance is the number of errored-seconds raised when the measured delay variance is greater than the configured DV threshold. The ES delay variance is calculated in milliseconds. |
ES DSCP |
ES DSCP is the number of errored-seconds occurred when the received DSCP value does not match the expected value. |
SES |
Severely errored second (SES) indicates the number of seconds that a SES threshold has been violated. |
First round trip delay percentile |
First round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first delay percentile slot. |
Second round trip delay percentile |
Second round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second delay percentile slot. |
First far end round trip delay percentile |
First far end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first far end round trip delay percentile slot. |
Second far end round trip delay percentile |
Second far end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second far end round trip delay percentile slot. |
First near end round trip delay percentile |
First near end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first near end round trip delay percentile slot. |
Second near end round trip delay percentile |
Second near end round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second near end round trip delay percentile slot. |
ES for first round trip delay percentile |
ES for first round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined first round trip delay percentile slot and an errored-second is raised. |
ES for second round trip delay percentile |
ES for second round trip delay percentile. If the delay exceeds the configured value, the packet is included in the defined second round trip delay percentile slot and an errored-second is raised. |
Round trip loss |
Round-trip loss indicates the percentage of TWAMP packets sent from Test Agent that were lost either on the way to the reflector or on the way back to Test Agent. The loss percentage is calculated by comparing the total packets lost with the total number of packets sent. |
Round trip lost |
Round-trip lost indicates the number of TWAMP packets sent from Test Agent that were lost either on the way to the reflector or on the way back to Test Agent. |
Timestamp samples |
The number of valid timestamp samples used in delay measurements. |
TWAMP Reflector |
|
Received packets |
Received packets indicates the number of packets received by the Test Agent from the reflector. |
Rate |
Rate indicates the rate at which Test Agent received TWAMP traffic. It is the aggregate of all the concurrent sessions. The rate is calculated as the size of the response received divided by the total response time. The rate is displayed in Megabits Per Second. |
Active sessions |
Active sessions indicate the number of currently active sessions on the specified reflector. |
Bytes received |
Bytes received indicates the total size of TWAMP traffic received during the report interval. The size also includes the header size. |
ES |
ES is the number of seconds during which errors occurred in a specific duration of time. It is the total number of error-seconds that any threshold was violated. The ES is calculated in milliseconds. |
ES rate |
ES Rate is the number of errored-seconds raised because the rate threshold was violated. The ES rate is calculated in milliseconds. |
RPM (HTTP, PING, TCP, UDP) |
|
Round trip time |
Round-trip time (RTT) measures the amount of time taken by the request packet to travel from Test Agent Devices to the remote endpoint and the response packet to travel from the remote endpoint to Test Agent Devices. RTT indicates the time delay between sending a request and receiving a response. RTT indicates the time delay between sending a request and receiving a response. |
Round trip jitter |
Jitter occurs when the packets experience a delay during a round trip, from the Test Agent to the remote endpoint. The delay is calculated in milliseconds. |
Round trip inter-arrival |
The Round-trip interarrival jitter indicates an estimate of the total statistical variance of a packet’s interarrival time as defined in IETF RFC 1889. The interarrival jitter is calculated in milliseconds |
Loss |
Loss indicates the percentage of request packets sent for which responses were not received. |
Analyze the Stream Graph
A stream graph is a graphical representation of a metric generated by a Stream over a period of time. You can generate multiple stream graphs for various metrics by enabling the corresponding toggle button.
In the stream graph, the X axis (horizontal) always represents the time duration of Test or Monitor. The Y axis (vertical) represents the metric value that is being measured.
For example, create a Test by adding an RPM Ping Task with the threshold value for Round Trip Time (RTT) set to 10 seconds (s). When you run this Test, the following graph is displayed in the Stream-Name Details page.
In this stream graph (Figure 1), the X axis represents the time duration of the Test (14:15:10 through 14:17:10) and the Y axis displays the RTT value (0 through 14 milliseconds).
From the stream graph, you can infer that the RTT has exceeded the threshold (> 10) value at 14:16:16. At this moment, because the RTT value reached 11.468 ms, which is greater than the specified threshold value, an event is generated.