UpdateHealthChecker

put

/20200501/networkLoadBalancers/{network_load_balancer_id}/backendSets/{backend_set_name}/healthChecker

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

Request

Supported Media Types
Path Parameters
Header Parameters
  • For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
  • Minimum Length: 1
    Maximum Length: 64
    A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
Body ()
The health check policy configuration details.
Root Schema : UpdateHealthCheckerDetails
Type: object
The configuration details of the health checker.
Show Source
  • DnsHealthCheckerDetails
    DNS healthcheck configurations.
  • Minimum Value: 1000
    Maximum Value: 1800000
    The interval between health checks, in milliseconds. Example: 10000
  • Minimum Value: 0
    Maximum Value: 65535
    The backend server port against which to run the health check. Example: 8080
  • Allowed Values: [ "HTTP", "HTTPS", "TCP", "UDP", "DNS" ]
    The protocol that the health check must use; either HTTP, UDP, or TCP. Example: HTTP
  • Base64 encoded pattern to be sent as UDP or TCP health check probe.
  • A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$
  • Base64 encoded pattern to be validated as UDP or TCP health check probe response.
  • 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. Example: 3
  • The status code a healthy backend server should return. If you configure the health check policy to use the HTTP protocol, then you can use common HTTP status codes such as "200". Example: 200
    Example: 0
  • Minimum Value: 1
    Maximum Value: 600000
    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. Example: 3000
  • The path against which to run the health check. Example: /healthcheck
Nested Schema : DnsHealthCheckerDetails
Type: object
DNS healthcheck configurations.
Show Source
  • Minimum Length: 1
    Maximum Length: 255
    The absolute fully-qualified domain name to perform periodic DNS queries. If not provided, an extra dot will be added at the end of a domain name during the query.
  • Allowed Values: [ "IN", "CH" ]
    The class the dns health check query to use; either IN or CH. Example: `IN`
  • Allowed Values: [ "A", "TXT", "AAAA" ]
    The type the dns health check query to use; A, AAAA, TXT. Example: `A`
  • rcodes
    Minimum Number of Items: 1
    Unique Items Required: true
    An array that represents accepetable RCODE values for DNS query response. Example: ["NOERROR", "NXDOMAIN"]
  • Allowed Values: [ "UDP", "TCP" ]
    DNS transport protocol; either UDP or TCP. Example: `UDP`
Nested Schema : rcodes
Type: array
Minimum Number of Items: 1
Unique Items Required: true
An array that represents accepetable RCODE values for DNS query response. Example: ["NOERROR", "NXDOMAIN"]
Show Source
  • Allowed Values: [ "NOERROR", "SERVFAIL", "NXDOMAIN", "REFUSED" ]
    Return code value to validate the DNS response in healthcheck.
Back to Top

Response

Supported Media Types

202 Response

Request accepted for processing.
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
  • Unique Oracle-assigned identifier for the asynchronous request. You can use this to query status of the asynchronous operation.

400 Response

Bad Request
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

401 Response

Unauthorized
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

404 Response

Not Found
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

409 Response

Conflict
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

412 Response

Precondition Failed
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

429 Response

Too Many Requests
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

500 Response

Internal Server Error
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.

Default Response

Unknown Error
Headers
  • Unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
  • A short error code that defines the error, meant for programmatic parsing. See [API Errors](https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm).
  • A human-readable error string.
Back to Top