OCI Load Balancer Response Health Test

This test continuously monitors the load balancers in the target Oracle Cloud Infrastructure and for each load balancer, this test reports the number of low/high latency responses and the percentage of SLA (Service Level Agreement) achieved. This will help the administrators to identify the load balancer that is under-performing due to various reasons and make corrective actions.

Target of the test: Oracle Cloud Infrastructure Load Balancer

Agent deploying the test: A Remote Agent

Outputs of the test: One set of results for each Region:Compartment:Log Group:Log that is being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed.
Host	The IP address of the target host to be monitored.
Tenancy ID	To monitor the target OCI Load Balancer, the eG agent has to be configured with the Tenancy ID of the user who is authorized to access the OCI Load Balancer. To know how to determine a Tenancy ID, refer to Generating an API Key.
Confirm Tenancy ID	Confirm the Tenancy ID by re-typing in the Confirm Tenancy ID text box.
Compartment ID	Specify the ID of the compartment in which the load balancer that you want to monitor is grouped, in the Compartment ID text box. To know how to view the Compartment ID, refer to Viewing the Compartment ID.
Confirm Compartment ID	Confirm the Compartment ID by re-typing in the Confirm Compartment ID text box.
User ID	Specify the ID of the user who is authorized to access the OCI Load Balancer in the User ID text box. You can either create a new user or use an existing user for this purpose. To create a new user and obtain the User ID of the user, refer to Pre-requisites for Monitoring Oracle Cloud Infrastructure Load Balancer.
Confirm User ID	Confirm the User ID by re-typing in the Confirm User ID text box.
Fingerprint	The fingerprint authenticates the API call, confirming its origin from the designated user i.e., the user who is authorized to access the target OCI Load Balancer. By default, the fingerprint is exposed while creating a new user and generating an API Key. Specify the fingerprint that you had noted down earlier while generating the API Key in the Fingerprint text box. To know how to identify the fingerprint, refer to Generating an API Key.
Confirm Fingerprint	Confirm the Fingerprint by re-typing in the Confirm Fingerprint text box.
Private Key File Path	Specify the full path to the Private Key that you have downloaded while generating an API key in the Private Key File Path text box. By default, the Private key is downloaded as a .pem file. For example, your location can be: /opt/egurkha/oci/oci_key.pem
Regions	Specify the region where the load balancer and its associated resources are tied to in the Regions text box. To know the region, refer to Generating an API Key.
Log Group Name	Specify the name of the Log group that holds log objects related to this Load Balancer in the Log Group Name text box.
Log Name	Specify the name of the log object in which the log entries generated by this load balancer is stored in.
Latency Seconds	Specify the time (in seconds) that is permissible for the load balancer to serve a request. The default is 2 seconds. So in this case, the responses that took lesser than 2 seconds will be categorized as fast responses and the responses that took more than 2 seconds will be categorized as slow responses.
Enable Fast Response Logs for DD	This flag is set to No by default indicating that this test will not report detailed diagnostics for Low Latency Responses measure. This means that the test, by default, will not capture and store the details of the slow responses in the log. However, if you want to view the list of slow responses, enable the detailed diagnosis capability of the Low Latency Responses measure by setting this flag to Yes.
Require All the Fast Response Logs for DD	This flag is set to No by default. This means that the test, by default, will not capture and store the details of all the fast responses in the log. However, if you want to view the list of all the fast responses, enable the Enable Fast Response Logs for DD flag by setting this flag to Yes.
No of Fast Response Logs for DD	Specify the number of fastest response logs that you want to view in this text box.
Require All the Slow Response Logs for DD	This flag is set to No by default indicating that this test will not report detailed diagnostics for High Latency Responses measure. This means that the test, by default, will not capture and store the details of the fast responses in the log. However, if you want to view the list of fast responses, enable the detailed diagnosis capability of the High Latency Responses measure by setting this flag to Yes.
No of Slow Response Logs for DD	Specify the number of slowest response logs that you want to view in this text box.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
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: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Low latency responses	Indicates the number of low latency responses this load balancer had fetched.	Number	A very high value of this measure is desired. A lower value of this measure indicates that the load balancer is under-performing or overloaded in some ways. Use the detailed diagnosis of this measure to find out the region, response code, type, data, ID, Oracle, Source, Spec Version, and time stamp of the load balancers who has low latency responses.
High latency responses	Indicates the number of high latency responses this load balancer had fetched.	Number	Higher value of this measure indicates backend server overload, bottlenecks, or network issues. Use the detailed diagnosis of this measure to find out the region, response code, type, data, ID, Oracle, Source, Spec Version, and time stamp of the load balancers who has high latency responses.
SLA achievement	Indicates the percentage of SLA achieved by this load balancer.	Percent	A low SLA achievement suggests there was a partial or full service outage, degraded performance, or an inability to manage resources properly. Administrators may need to analyze logs and metrics to understand the root cause.