Fabric Health Analytics for Virtual Resources
Fabric Health Analytics (FHA) in GigaVUE-FM is a standalone service that provides data visualization capabilities. Using FHA1 you can create visual elements such as charts that are embedded as visualizations. The visualizations are grouped together in dashboards. You can also create search objects using FHA. Dashboards, Visualizations and Search Objects are called FHA objects. Refer to Fabric Health Analytics topic for more detailed information on Fabric Health Analytics.
Rules and Notes:
- You cannot edit or delete these default dashboards. However, you can clone the dashboards and visualizations. Refer to the Clone Dashboard section for more details.
- Use the Time Filter option to select the required time interval for which you need to view the visualization.
Virtual Inventory Statistics and Cloud Applications Dashboard
Fabric Health Analytics dashboards allow users to monitor the physical and virtual environment and detect anomalous behavior and plan accordingly. Refer to the Fabric Health Analytics section for details on how to create a new dashboard, clone a dashboard, create a new visualization, and other information about the Discover page and Reports page.
To access the dashboards:
- Go to -> Analytics -> Dashboards.
- Click on the required dashboard to view the visualizations.
The following table lists the various virtual dashboards:
Dashboard |
Displays | Visualizations | Displays | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Inventory Status (Virtual)
|
Statistical details of the virtual inventory You can view the following metric details at the top of the dashboard:
You can filter the visualizations based on the following control filters:
|
V Series Node Status by Platform |
Number of healthy and unhealthy V Series Nodes for each of the supported cloud platforms.
|
||||||||||||
Monitoring Session Status by Platform | Number of healthy and unhealthy monitoring sessions for each of the supported cloud platforms | ||||||||||||||
Connection Status by Platform | Number of healthy and unhealthy connections for each of the supported cloud platforms | ||||||||||||||
GCB Node Status by Platform | Number of healthy and unhealthy GCB nodes for each of the supported cloud platforms | ||||||||||||||
V Series Node Statistics |
Displays the Statistics of the V Series node such as the CPU usage, trend of the receiving and transmitting packets of the V Series node. You can filter the visualizations based on the following control filters:
|
V Series Node Maximum CPU Usage Trend |
Line chart that displays maximum CPU usage trend of the V Series node in 5 minutes interval, for the past one hour. Note: The maximum CPU Usage trend refers to the CPU usage for service cores only. Small form factor V-series nodes do not have service cores, therefore the CPU usage is reported as 0. |
||||||||||||
V Series Node with Most CPU Usage For Past 5 minutes |
Line chart that displays Maximum CPU usage of the V Series node for the past 5 minutes. Note: You cannot use the time based filter options to filter and visualize the data. |
||||||||||||||
V Series Node Rx Trend | Receiving trend of the V Series node in 5 minutes interval, for the past one hour. | ||||||||||||||
V Series Network Interfaces with Most Rx for Past 5 mins |
Total packets received by each of the V Series network interface for the past 5 minutes. Note: You cannot use the time based filter options to filter and visualize the data. |
||||||||||||||
V Series Node Tunnel Rx Packets/Errors | Displays the reception of packet at the Tunnel RX. This is the input to V Series Node, Grouping by tunnel identifier comprising {monDomain, conn, VSN, tunnelName}, before aggregation. | ||||||||||||||
V Series Node Tunnel Tx Packets/Errors | TX is for output tunnels from VSN. V Series Node Tunnel Tx Packets/Errors | ||||||||||||||
Dedup |
Displays visualizations related to Dedup application. You can filter the visualizations based on the following control filters:
|
Dedup Packets Detected/Dedup Packets Overload | Statistics of the total dedup packets received (ipV4Dup, ipV6Dup and nonIPDup) against the dedup application overload. | ||||||||||||
Dedup Packets Detected/Dedup Packets Overload Percentage | Percentage of the dedup packets received against the dedup application overload. | ||||||||||||||
Total Traffic In/Out Dedup | Total incoming traffic against total outgoing traffic | ||||||||||||||
Tunnel (Virtual) |
Displays visualizations related to the tunneled traffic in both bytes as well as the number of packets. You can select the following control filters, based on which the visualizations will get updated:
The following statistics are displayed for the tunnel:
|
Tunnel Bytes |
Displays received tunnel traffic vs transmitted tunnel traffic, in bytes.
|
||||||||||||
Tunnel Packets | Displays packet-level statistics for input and output tunnels that are part of a monitoring session. | ||||||||||||||
App (Virtual) |
Displays Byte and packet level statistics for the applications for the chosen monitoring session on the selected V series node. You can select the following control filters, based on which the visualizations will get updated:
By default, the following statistics are displayed:
|
App Bytes | Displays received traffic vs transmitted traffic, in Bytes. | ||||||||||||
App Packets
|
Displays received traffic vs transmitted traffic, as the number of packets. | ||||||||||||||
End Point (Virtual) |
Displays Byte and packet level statistics for the un-tunneled traffic deployed on the V-series nodes. The following statistics that are shown for Endpoint (Virtual):
The endpoint drop-down shows <V-series Node Management IP address : Network Interface> for each endpoint. You can select the following control filters, based on which the visualizations will get updated:
|
Endpoint Bytes | Displays received traffic vs transmitted traffic, in Bytes. | ||||||||||||
Endpoint Packets | Displays received traffic vs transmitted traffic, as the number of packets. |
Note: The Tunnel (Virtual), App (Virtual) and Endpoint (Virtual) dashboards do not show data from the previous releases if the Monitoring Session [Platform : Domain : Connection] dashboard filter is applied. This is because, this filter relies on the new attributes in the Elasticsearch database, which are available only from software version 5.14.00 and beyond.