OCI Load Balancer Access Log 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 traffic patterns by tracking the number of HTTP 3xx (redirects), 4xx (client errors), and 5xx (server errors) responses. These metrics help assess application performance, detect misconfigurations, and identify potential backend 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 Region:Load Balancer 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.

Load Balancer

Specify the name of the load balancer for which you want to monitor the access logs in the Load Balancer 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

Total responses

Indicates the total number of responses made by this load balancer.

Number

 

2xx SLA achievement

Indicates the percentage of successful HTTP responses (status codes in the 2xx range) delivered by this load balancer.

Percent

 

HTTP 200 responses

Indicates the total number of HTTP 200 responses made by this load balancer.

Number

 

HTTP 2xx responses

Indicates the total number of 2xx responses made by this load balancer.

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 this load balancer.

Number

The value of this measure denotes the number of responses by this load balancer that needs further action.

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 balancer that had responded with this error.

HTTP 4xx responses

Indicates the total number of 4xx responses made by this load balancer.

Number

The value of this measure denotes the number of responses made by this load balancer that has bad syntax or cannot be fulfilled.

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 balancer that had responded with this error.

HTTP 5xx responses

Indicates the total number of 5xx responses made by this load balancer.

Number

The value of this measure denotes the number of responses by this load balancer where the server failed to fulfill a valid request.