OCI Load Balancer Listener HTTP Statistics Test

This test continuously monitors the load balancers in the target Oracle Cloud Infrastructure and for each load balancer, this test reports the HTTP responses grouped into successes, redirects, client errors, and server errors. This helps identify availability issues.

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 Load Balancer:Listener:Active Domain ID 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.
Port	Specify the port at which the specified host listens to.
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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total responses	Indicates the total number of responses made by the load balancer in this domain.	Number
2xx SLA achievement	Indicates the percentage of of successful HTTP responses (status codes in the 2xx range) delivered by the load balancer in this domain.	Percent
HTTP 200 responses	Indicates the total number of HTTP 200 responses made by the load balancer in this domain.	Number
HTTP 2xx responses	Indicates the total number of 2xx responses made by the load balancer in this domain.	Number	The value of this measure denotes the number of responses by this load balancer that were successful.
HTTP 3xx responses	Indicates the total number of 3xx responses made by the load balancer in this domain.	Number	The value of this measure denotes the number of responses by this load balancer that needs further action.
HTTP 4xx responses	Indicates the total number of 4xx responses made by the load balancer in this domain.	Number	The value of this measure denotes the number of responses by this load balancer that has bad syntax or cannot be fulfilled.
HTTP 5xx responses	Indicates the total number of 5xx responses made by the load balancer in this domain.	Number	The value of this measure denotes the number of responses by this load balancer where the server failed to fulfill a valid request.
HTTP 502 responses	Indicates the number of HTTP 502 responses received by the load balancer in this domain.	Number	When this response code is encountered by the load balancer, the load balancer is usually healthy, but one or more of the backend servers are failing or misbehaving.
HTTP 504 responses	Indicates the number of HTTP 504 responses received by the load balancer in this domain.	Number	When this response code is encountered by the load balancer, it means the load balancer gave up waiting for a response from the backend before the timeout threshold.