Proxy Network Test
Network proxy facilitates comm/unication between pods and services within a cluster. It handles routing, load balancing, and service discovery, ensuring seamless connectivity, managing traffic efficiently, and enabling reliable interactions between containerized applications across the cluster.
Monitoring network proxies is essential for ensuring application performance, security, and reliability. It helps identify bottlenecks, latency issues, and unusual traffic patterns that could indicate security threats. By tracking performance metrics and error rates, teams can quickly troubleshoot issues, optimize configurations, and maintain compliance with SLAs. Proactive monitoring fosters a better user experience and supports efficient resource utilization in a dynamic environment.
The Proxy Network Test continuously monitors the Proxy Network in the target node and reports key metrics like number of request latency, total request latency etc.
Target of the test : A Kubernetes Worker Node
Agent deploying the test : An internal agent
Outputs of the test : One set of results for the target Kubernetes Worker node being monitored
|
Parameter |
Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the host for which this test is to be configured. |
|
Port |
Specify the port at which the specified Host listens. By default, this is 6443. |
|
Timeout |
Specify the duration (in seconds) beyond which the test will timeout in the Timeout text box. The default value is 10 seconds. |
|
Metric URL |
Each of the Kubernetes system components expose monitoring metrics through /metrics endpoint of the HTTP server. Specify the metric endpoint URL in the Metric URL textbox. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
|
Measurement |
Description |
Measurement Unit |
Interpretation |
|---|---|---|---|
|
Requests |
Indicates the number of requests with latency. |
Number |
Monitoring request latency effectively can lead to enhanced performance, better resource management, and improved user satisfaction.
|
|
Total request latency |
Indicates the total request latency across the requests. |
Milliseconds |
|
|
Number of client certificate rotation |
Indicates the number of client certification rotation. |
Number |
If the number of rotations is too high, the validity of certificates need to be increased. |
|
Total client certificate rotation |
Indicates the total number of client certification rotations on the target node. |
Number |
If the number of rotations is too high, the validity of certificates need to be increased. |
|
Client execution plug-in TTL |
Indicates the time taken for execution of client execution of plug - in. |
Seconds |
|
|
Total requests |
Indicates the total number of requests received on the target node. |
Number |
If the total number of requests is too high, the server resources will be exhausted. |
|
Average client certificate rotation |
Indicates the average client certificate rotations over the given period of time. |
Number |
Average number of rotations gives you the better picture, with any periodic spikes evened out. |
|
Average request latency |
Indicates the average request latency over the number of requests received since last measurement. |
Milliseconds |
If the average request latency is too high, then it could be because of high number of requests or any network issue. |