Accessing the CloudTracer Screen
To view data metrics, open to the CloudTracer screen by clicking CloudTracer on the CloudVision Portal (CVP).
This screen is divided into the following two panels:
Left Panel of the CloudTracer Screen
This panel provides the following metric options:
- Metric pane - Click any of the following entities to view the corresponding
current metric for n connections where n is the count of selected devices and
- HTTP Response Time
- Packet Loss
- Connections pane
- Device or host search string - Type the device or host name for a quick search
- Configured devices - Select the required devices and hosts to view corresponding metrics
- Clear All - Click to clear all selections
Right Panel of the CloudTracer Screen
This panel displays metrics of selected options in the following ways:
- Current information of the
selected metric type from selected devices and hosts
Note: Metrics are streamed whenever data is gathered on EOS switches. The default interval to query metrics data is five seconds.
- Click on a metric to view detailed information.
The upper panel of this screen provides graphical presentation of the metric. The lower panel of this screen displays the metric through following categories:
- Metric History tab -
Displays the metric history ranging from the last hour to the last week.
Click the required timeline to view corresponding metrics.Note: Click Zoom In and Zoom Out options to view metrics ranging from every 15 minutes to every minute.
- Raw Data tab - Displays indexes, timestamps, and values of raw data.
- Data Paths tab - Displays keys and data paths
used to compute the data for this metric. Note: Clicking required link navigates to the corresponding path in the telemetry browser.
- Statistics tab - Displays statistics of the selected device.
- Hover the cursor on metric to view metrics from all metric types.
CloudTracer Latency Anomaly Events
The cloudtracer latency anomaly event monitors the latency metric between devices and configured hosts. The events are designed to alert the user when the latency between a device and a configured host is outside of recent historical bounds.
Figure 8 is a sample event view for one of these events between the device with hostname `Oslo` and the cloudtracer host endpoint `www.bbc.co.uk`.
Figure 9 explains various stages of this event.
Prior to this event in Figure 9, the latency metric (green line in upper graph) is stable with minimal deviations. The historical bounds (blue shaded region) that determine when the metric is in a normal state has a small range with both the upper and lower bounds near the historical mean (dark blue line). The historical bounds are computed by adding and subtracting a fixed multiple of the current latency standard deviation to the current mean.
The anomaly score starts to increase from zero when the latency value strays outside of the historical bounds. The latency values that are outside the bounds are highlighted in red. The anomaly score is the total number of standard deviations outside the historical bounds. The anomaly score is the positive cumulative sum of the number of standard deviations outside of the historical bounds. For example, if the bounds are set as 3 standard deviations outside of the mean and we get a value of the latency that is 5 times the standard deviation away from the mean, the anomaly score will increase by 2. If the next latency value was 1.5 times the standard deviation outside of then mean then we would subtract 1.5 from the anomaly score. The anomaly score therefore keeps track of the cumulative deviation of the latency outside of the historical bounds. It is bounded below by zero.
Figure 10 provides a detailed explanation on computing the anomaly score.
The event is generated when the anomaly score exceeds a threshold for a set period of time.
The anomaly score starts to decrease when the latency values are inside the historical bounds. The historical bounds have increased based on recent deviations in latency which makes the system less sensitive than prior to the event. The event ends when the anomaly score is below the threshold for a set period of time.
Figure 11 provides a detailed explanation of the anomaly score decreasing when an event ends.
At the end of the time range, historical bounds are narrowing as the latency has now returned to a stable value with minimum deviations. The history needs approximately six hours to have negligible impact on the statistics and bounds.
This screen also provides the following additional metrics of this event (see Figure 12):
The other CloudTracer metrics are displayed for this device and host pair
The latency metric between other devices and this host
The latency metric between this device and other hosts
Connectivity Monitor with VRF Support
Connectivity Monitor with VRF support allows you to configure multiple VRFs for each host and multiple source interfaces within each host on each device.
Enabling Connectivity Monitor with VRF Support
To enable Connectivity Monitor with VRF support, the feature must be enabled from the Settings page.
- Select the Setting icon to open the General Settings page.
- Select the toggle for Connectivity Monitor VRFs and Interfaces (Beta).
Viewing Connectivity Monitor with VRF Support
To view Connectivity Monitor with VRF Support, select Connectivity Monitor from the Devices tab.
- Selecting the checkbox next to a VRF name will select all source interfaces on the VRF.
- Selecting the checkbox next to the name of the host will select all VRFs and all source interfaces within each VRF.
- Selecting the checkbox next to the device name will select every host configuration available on the device.