Editing Network Load Balancer Health Check Policies

Update the health check policy for a network load balancer and backend set.

    1. Open the navigation menu, click Networking, and then click Load balancers. Click Network load balancer. The Network load balancers page appears.
    2. Select the Compartment from the list. All network load balancers in that compartment are listed in tabular form.
    3. Select a State from the list to limit the network load balancers displayed to that state.
    4. Select the network load balancer for whose health check policies you want to edit. The network load balancer's Details page appears.
    5. Click Backend sets under Resources. The Backend sets list appears. All backend sets are listed in tabular form.
    6. Click the backend set whose details you want to get. The backend set's Details page appears.
    7. Click Update health check. You can also click the Actions menu (Actions Menu) for the backend set whose health check you want to update and select Update health check. The Update health check dialog box appears.
    8. Update any of the following:
      • Protocol: Specify the protocol:

        • HTTP

        • HTTPS

        • TCP

        • UDP

        Configure your health check protocol to match your application or service. See Health Check Policies for Network Load Balancers.

      • Port: Specify the backend server port against which to run the health check. You can enter the value '0' to have the health check use the backend server's traffic port.

      • Interval in MS: Specify how frequently to run the health check, in milliseconds. The default is 10000 (10 seconds).

      • Timeout in MS: Specify the maximum time in milliseconds to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. The default is 3000 (3 seconds).

      • Number of retries: Specify the number of retries to attempt before a backend server is considered "unhealthy." This number also applies when recovering a server to the "healthy" state. The default is 3.

      • Status code: (HTTP and HTTPS only) Specify the status code a healthy backend server must return.

      • URL path (URI): (HTTP and HTTPS only) Specify a URL endpoint against which to run the health check.

      • Response body regex: (HTTP and HTTPS only) Provide a regular expression for parsing the response body from the backend server.

      • Request data: (TCP and UDP only) Required for UDP, optional for TCP. Enter a text string. The network load balancer health check sends the text string, for example "hello," as part of the initial TCP or UDP probe to the backend servers and awaits a response.

      • Response data: (TCP and UDP only) Required for UDP, optional for TCP. Enter a text string. The backend servers respond to the initial TCP or UDP request probe from the health check with this text string. For example if the response data is set to "hello" and the server responds with "This is server A, hello!" it's considered a match and the network load balancer's health check consider the probe a success.

    9. Click Save changes.
  • Use the oci nlb health-checker update command and required parameters to edit the health check policies of a network load balancer:

    oci nlb health-checker update --backend-set-name backend_set_name --network-load-balancer-id network_load_balancer_ocid [OPTIONS]

    For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

  • Run the UpdateHealthChecker operation to edit a health check policy of a backend set for a load balancer.