Document health monitor UDP-CONNECT type
Change-Id: I95bd60cd69f1823897bbd737c537df421b16aec9
This commit is contained in:
parent
4da644136e
commit
ee0b566d39
@ -1169,7 +1169,8 @@ and validated with the following exceptions:
|
||||
| | | be less than the delay value. |
|
||||
+-----------------------+--------+------------------------------------------+
|
||||
| type | string | The type of health monitor. One of HTTP, |
|
||||
| | | HTTPS, PING, TCP, or TLS-HELLO. |
|
||||
| | | HTTPS, PING, TCP, TLS-HELLO or |
|
||||
| | | UDP-CONNECT. |
|
||||
+-----------------------+--------+------------------------------------------+
|
||||
| url_path | string | The HTTP URL path of the request sent by |
|
||||
| | | the monitor to test the health of a |
|
||||
|
@ -606,8 +606,8 @@ generates the health check in your web application:
|
||||
|
||||
Other heath monitors
|
||||
--------------------
|
||||
Other health monitor types include ``PING``, ``TCP``, ``HTTPS``, and
|
||||
``TLS-HELLO``.
|
||||
Other health monitor types include ``PING``, ``TCP``, ``HTTPS``, ``TLS-HELLO``,
|
||||
and ``UDP-CONNECT``.
|
||||
|
||||
``PING`` health monitors send periodic ICMP PING requests to the back-end
|
||||
servers. Obviously, your back-end servers must be configured to allow PINGs in
|
||||
@ -627,6 +627,11 @@ In this case, using ``TLS-HELLO`` type monitoring is an alternative.
|
||||
SSLv3 client hello messages. It will not check any other health metrics, like
|
||||
status code or body contents.
|
||||
|
||||
``UDP-CONNECT`` health monitors do a basic UDP port connect. Health monitors
|
||||
of this type may not work correctly if Destination Unreachable (ICMP type 3) is
|
||||
not enabled on the member server or is blocked by a security rule. A member
|
||||
server may be marked as operating status ONLINE when it is actually down.
|
||||
|
||||
|
||||
Intermediate certificate chains
|
||||
===============================
|
||||
|
Loading…
Reference in New Issue
Block a user