The Node Detail screen provides configuration information about a specific Node, as well as the Node's recent utilization metrics and details about its Instances.
To access the Node Detail screen, navigate to the Nodes List, locate the desired Node, and click its name. This brings you to the Node Detail screen. Each section of this screen is detailed below.
Source
At the top you will see the Source field, which shows the Node you have selected. To view details for a different node, click the Source button and select another Node.
Node Summary
Below the Source Field you will see the Node Summary bar, which displays general information about the node, including the following:
| Name | Unique name assigned to this Node |
| Network Type | The type of network the Node is connected to
|
| Location | The geographic location of the Node |
| OS version | The operating system running on the node's instances |
| Package | The name of the Package the node supports, which defines the set of monitors the Node can run. (Applies to Enterprise Nodes only.) |
| Model | The Node model number (numeric value indicates the number of browser-based Tests each instance can run simultaneously)
*Note that if an error icon is displayed next to the model number, this means the number of instances assigned to the Node is insufficient. |
| # Active Instances | The number of individual machines (physical or virtual) assigned to the node. |
| # Utilized Instances | The maximum number of Instances that will consume licenses and be utilized to run tests at any one time. If # Utilized Instances is set to a value lower than # Active Instances, then the extra active instances function as back-ups, and will automatically start running tests if/when another Instance goes down or becomes unreachable. |
| Capacity | The total number of browser-based tests the Node can run simultaneously (calculated by multiplying the numeric portion of the model number by the number of instances) |
You can use the Edit button to the right of the Node Summary information to view/edit Node Properties.
Utilization
Next you will see the Utilization section, which contains several charts detailing recent utilization metrics.
Test Run Chart
This chart lists all Tests that were run at least once by the node during the last 1 hour. It includes the following information for each Test:
| Test Name | Unique name of the Test |
| Division | The specific division that the Test is assigned to |
| # Runs | The number of individual Test Runs for the Test during the last 1 hour |
| % Usage | The Test's percentage of total runs from the last hour (calculated by dividing this Test's # Runs by the total # Runs for all Tests) |
| % Downtime | The percentage of this Test's Runs that failed |
Click the name of any test to view its properties, or click the ellipses next to any test to access its Smartboard, Performance Charts, or Records.
Run Rates vs. Slippage Graph
This line graph plots the percentage of Test Runs that successfully executed and returned a response during the last 24 hours versus requests that "slipped." Each Node regularly connects to Catchpoint's servers to find out what tests it should run next, and to return results from prior test runs. Request Slippage refers to test runs that were scheduled in Catchpoint, but which the node did not request. Run Rate refers to the remaining test runs where the Node successfully requested the test and then returned a result.
Node Performance Graphs
These line graphs show how much of the Node's capacity is being used by each monitor type, as well as average Test performance by monitor. Each line color represents a different monitor, and you can expand the Legend to see which monitor each line color represents.
Capacity Utilization %
This graph shows the percentage of the Node's total capacity utilized by each monitor type.
All Errors (#) \ Errors by Group (#)
The All Errors (#) graph shows the total number of errors that occured across all tests.
The Errors by Group (#) graph shows how many errors occurred broken down by test type grouping.
Tests (#) \ Unique Tests (#)
The Tests (#) graph shows the total number of individual test runs by monitor type.
The Unique Tests (#) graph shows how many different unique test configurations were represented among these test runs, regardless of how many test runs each test had.
For example, if 10 different Tests were executed 5 times each during a given hour, then the All Test Runs (#) would be 50, and the Unique Tests (#) would be 10.
Avg. Test Time
This graph shows the average test time in milliseconds for each monitor type.
Instances
This section displays information related to the Instances (unique physical or virtual machines) that compose the selected Node.
Instances List
The Instances list shows each Instance assigned to the Node, and displays the following details for each Instance:
| ID | The unique numeric ID identifying the instance |
| Instance Name | The name assigned to the instance |
| Status |
|
| OS | The operating system version running on the instance |
| Hardware | The make/model/description of the physical hardware the instance is running on (if applicable. NA for virtualized instances.) |
| Cores | The number of processor cores on the instance |
| Memory | The amount of memory available on the instance in gigabytes |
| Version | The version of Catchpoint's Agent software running on the instance |
| Chrome | The version(s) of Chrome supported by the instance for Chrome monitor tests |
| Internal IP | The internal-network-facing IP address of the instance |
| External IP | The external (internet-facing) IP address of the instance |
| DNS | The DNS lookup server address configured on the instance |
| Proxy | The Proxy server address configured on the instance (if any) |
| Last Contact | The date and time when the instance last communicated with Catchpoint Command & Control |
You can access the properties page for any Instance by clicking its name in the list.
Hardware Usage Graphs
The graphs in this section show each active instance's hardware usage stats for the last 24 hours, including CPU usage, Memory usage, and Disk Space usage. This can be helpful for troubleshooting node performance issues and capacity planning.
