How to: Review the health and traffic of a BIG-IP Next instance¶
Description: This document describes how to review the health and traffic of a managed BIG-IP Next instance using BIG-IP Next Central Manager. If you are using VELOS, it is important to note that data represented VELOS represents each tenant (BIG-IP Next instance), and does not reflect the instance as a whole.
Overview¶
Reviewing a BIG-IP Next instance that is managed by BIG-IP Next Central Manager allows you to monitor its performance and health. You can use this information to identify trends that might impact the BIG-IP Next instance’s performance.
Health - The health of each BIG-IP Next instance is monitored via resource usage data. For details about the data presented, see Health Statuses.
Traffic - Viewing the volume and management of traffic to each managed BIG-IP Next instance provides you latency information about the end-to-end transaction management. For details about the data presented, see [BIG-IP Next Instance Traffic Reporting] (#big-ip-next-instance-traffic-reporting).
Prerequisites¶
To manage BIG-IP Next instances, you must have Administrator or Instance Manager user credentials. Users with Application Manager and Auditor credentials have read-only access to all application service information. For more information about user roles, see How to: Assign standard roles to users.
To view data you must have at least one deployed BIG-IP Next instance.
You must have user permission to view BIG-IP Next instances.
Review BIG-IP Next Instance Data¶
Log in to BIG-IP Next Central Manager, click the workspace switcher next to the F5 icon, and click Infrastructure.
The My Instances screen provides a list of the managed BIG-IP Next instances.
Click the name of a BIG-IP Next instance.
A panel displays the BIG-IP Next instance’s properties.
To review BIG-IP Next instance data:
Click Health to view the BIG-IP Next instance’s Total CPU Usage and Memory over the past hour.
Click Traffic to view the BIG-IP Next instance’s Transaction Outcomes, New Connections, Concurrent Connections, and Throughput.
Click Network Interface to view the BIG-IP Next instances data based on the network interface selected.
To view new incoming data, click Refresh.
Note: Be sure to refresh each time you want to view the newest data.
Click Exit to close the data for this BIG-IP Next instance.
Click Exit to close the BIG-IP Next instance properties.
Health Statuses¶
Healthy - The BIG-IP Next instance is active. For HA BIG-IP Next instances, this status indicates that at least one instance is responsive and active.
Critical - The BIG-IP Next instance is inactive. For HA BIG-IP Next instances, this status indicates that both instances are unresponsive and inactive.
Health Charts¶
Health charts display the resource usage of the selected BIG-IP Next instance. Charts present data collected from the past hour.
Total CPU Usage¶
The total CPU usage is analyzed based on the major activities of the BIG-IP Next instance. Unit - Percent (%) CPU used
Metrics:
User - The average percentage of CPU used for user space programs.
System - The average CPU usage for all the BIG-IP Next instance system processes.
I/O Wait - The percentage of time CPU is idle for an I/O wait operation. This occurs when at least one outstanding I/O disk operation is scheduled on system CPU.
Stolen - The percentage of time a virtual CPU waits for real CPU.
Memory¶
The percentage of RAM used by the BIG-IP Next instance processes of the managed instance. Unit - The average percent (%) RAM used. Metrics:
Total - The average percentage of RAM used by all BIG-IP Next instance processes.
Disk Usage¶
The average rate of traffic (in Giga Bytes per second) the BIG-IP instance reads or writes from the hard disk data. Unit - The Giga Bytes of traffic per second (GB/s). Metrics
Read - The average rate at which traffic to a BIG-IP instance reads from the hard disk.
Write - The average rate at which traffic to a BIG-IP instance writes to the hard disk.
BIG-IP Next Instance Traffic Reporting¶
Traffic Charts¶
The average cumulative values of traffic to all applications for a single BIG-IP Next instance over the past hour.
HTTP Transactions¶
The outcome assigned to each HTTP request as they are processed by the BIG-IP Next instance. Unit - The average number of transactions per second (Avg TPS). Metrics:
Passthrough - HTTP transactions that completed the request and response exchange.
Incomplete - HTTP transactions that did not complete the entire request and response exchange.
Cached - HTTP Requests stored by the BIG-IP Next instance to reduce the traffic load on back-end servers.
Response - HTTP requests that received a response directly from the BIG-IP Next instance.
New Connections¶
The total number of new connections opened for applications configured to the BIG-IP Next instance either from the client side or server side. Unit - The average number of new connections per second (Avg/s). Metrics:
Client Side - The total number of new requests opened at the client side.
Server Side - The total number of new responses opened at server side.
Concurrent Connections¶
jwong: Missing png file
The number of connections that are open at the same time on the client and on the server side.
Unit - The number of concurrent connections (Count). Metrics:
Client Side - The number of concurrent connections at the client side.
Server Side - The number of concurrent connections at the server side.
Throughput¶
The average rate of traffic in bytes per second processed by the BIG-IP Next instance.
Unit - The number of bytes per second (Bytes/s). Metrics:
Requests - The average rate of bytes per second sent in transaction requests.
Responses - The average rate of bytes per second sent in transaction responses.