The Machine Health panel indicates current metrics on the counts and general health of each process that is running on the PCA server.
| Setting | Description |
|---|---|
Name |
Name of PCA pipeline process |
Running |
Count of processes running on the PCA server |
KB Size High |
Maximum size in kilobytes used by all instances of the process since the PCA last restarted. |
CPU % High |
Maximum RAM consumption as a percentage of the available memory on the CPU since the PCA last restarted. |
Mount Stats
You can review stats on the configured mount points on the PCA server.
| Setting | Description |
|---|---|
Mount Point |
Path from root of the specified mount point |
Usage |
Percent of available RAM used by the mount point |
Available |
Available RAM used by the mount point |
Peers
The Peers panel indicates the connectivity between the PCA server and the Transport Service servers, which process data captured by the PCA.
| Setting | Description |
|---|---|
Delivery Host or Address |
Host name or static IP address of the peer |
Port |
Port that is used to communicate with the Transport Service peer. Typically, port
1966 or 1967 is used. |
Status |
Current status: disconnected or connected |
Hits Delivered |
Count of hits that are sent from delivered to the peer since the PCA last restarted |
Hits Dropped |
Count of hits since the PCA last restarted that were not acknowledged by the peer and
therefore dropped. Note: Non-zero values must be investigated with the administrators of the
Transport Service server, as they can be indicative of connectivity issues or issues in the
processing of hits in the Windows™
pipeline. |
Current Per Second Stats
For each instance of the PCA, this panel indicates the flow of hits through each process of the application on a per-second basis. This refreshes every 20 seconds by default.
| Setting | Description |
|---|---|
ID |
Identifier of the instance |
Listend Packets In |
Count of packets that are entering the listend process. This metric indicates the rate of packets that are received by the PCA from the network. |
Listend Out |
Volume of data that is leaving the listend process per second. |
Reassd In |
Volume of data that is expected to enter the reassd process per second. This metric must
match the volume leaving the listend process. Differences between the values of |
TCP Connections |
Count of TCP connections between the PCA and the switch or span submitting data to it |
SSL Missing Keys |
Count of missing SSL keys per second. Note: This value must be zero. Non-zero values can
indicate issues to investigate. |
SSL New Handshakes |
Count of new SSL handshakes detected in the capture stream per second. Typically, this
metric indicates the count of new sessions. Note: Consistently abnormal values can indicate that the
web server is initializing new SSL handshakes when it must not, which can indicate a server-side
configuration issue. |
Reassd Hits Non-SSL |
Count of non-SSL hits that are entering the reassd process per second |
Reassd Hits SSL |
Count of SSL hits that are entering the reassd process per second |
Reassd Out |
Count of hits that are leaving the reassd process per second |
Additional PCA web console debugging information
- Get tcpdumps of the network traffic that is delivered to the PCA. This data can be useful in assessing whether issues are occurring within the PCA or elsewhere in the enterprise network infrastructure.
- Statistical information can be downloaded in the Statistics log.
- If the PCA has generated a core dump due to a major error, you can download the core dump and other data through the Debug page, which is accessible from a link on the Summary tab.
- More information is available in the PCA logs.