OCI Load Balancer Backend Status Test
A backend server refers to an individual server that is part of a backend set in a load balancer configuration. These servers handle the actual processing of client requests that are routed through the load balancer. Each backend server is registered in a backend set, which is the group of servers the load balancer distributes traffic to.
This test continuously monitors the individual backend servers in the target Oracle Cloud Infrastructure and for each individual backend server, this test reports the status of the backend server. This will help the administrators to identify unhealthy instances and ensure reliable traffic distribution across backend servers.
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:Backend Set:Backend server that is being monitored.
|
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. |
|
Measurement |
Description |
Measurement Unit |
Interpretation |
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Backend status |
Indicates the current status of this backend server. |
|
The values of this measure and their corresponding numeric values are listed below:
Note: By default, this measure reports one of the Measure Values listed in the table above to indicate the current status of each backend server. In the graph of this measure however, the values will be represented using the numeric equivalents. |