All Products
Search
Document Center

View alert logs

Last Updated: Mar 26, 2021

What are alert logs?

Alert logs are generated by GTM if the following behaviors occur: a. The health check feature detects abnormal addresses and the addresses become available. b. Address pool sets are unavailable and become available. c. Access policies are switched.

Description

The health check feature detects abnormal addresses

Alert logs are generated if the health check feature detects abnormal addresses. Each log entry includes the time when an error occurs, an abnormal address, and an error code. You can identify the cause based on the error code. The following table describes common error codes.

Protocol

Status code

Description

HTTP

610

The error code returned because the connection or the Secure Sockets Layer (SSL) certificate exchange timed out. The timeout period is 30s.

HTTP

613

The error code returned because an error occurred during DNS resolution.

HTTP

615

The error code returned because the expected content is not found in the response.

HTTP

616

The error code returned because the authentication failed.

HTTP

611

The error code returned because the monitoring failed due to other causes.

Ping

550

The error code returned because the network connection failed.

Ping

610

The error code returned because no response was returned within 2s for any of the packets that were sent.

Ping

613

The error code returned because the hostname failed to be resolved to an IP address.

TCP

550

The error code returned because the socket failed to be opened. This error occurs when system resources are insufficient.

TCP

610

The error code returned because no response was returned or the response timed out.

TCP

611

The error code returned because the connection timed out or was rejected.

TCP

615

The error code returned because the expected content is not found in the response.

UDP

550

The error code returned because the socket failed to be opened. This error occurs when system resources are insufficient.

UDP

611

The error code returned because the hostname failed to be resolved and the connection failed.

UDP

610

The error code returned because the request failed to be sent or the response failed to be received.

UDP

615

The error code returned because the expected content is not found in the response.

DNS

610

The error code returned because an error occurred during DNS resolution.

DNS

613

The error code returned because the DNS query failed.

DNS

615

The error code returned because the expected content is not found in the response.

Unavailable addresses become available

Alert logs are generated if the health check feature detects that unavailable addresses become available. Each log entry includes a recovery time and an address.

Address pool sets become unavailable

If the number of available IP addresses in an address pool set is less than the value of the Min. Number of Available Addresses parameter, GTM determines that the address pool set is unavailable. A log entry is generated in this case. Each log entry includes a specific time, the name of an address pool set, the name of an access policy, an address pool type, and the minimum number of available addresses.

Unavailable address pool sets become available

If the number of available IP addresses in an address pool set is at least the value of the Min. Number of Available Addresses parameter, GTM determines that the address pool set is available. A log entry is generated in this case. Each log entry includes a specific time, the name of an address pool set, the name of an access policy, an address pool type, and the minimum number of available addresses.

Primary address pool sets switch to secondary address pool sets

If a primary address pool set that is associated with an access policy is unavailable, GTM switches to a secondary address pool set. A log entry is generated in this case. Each log entry includes a specific time, the name of an access policy, the name of an address pool set, and the minimum number of available addresses.

Procedure

1 . Log on to the Alibaba Cloud DNS console.

2 . In the left-side navigation pane, click Global Traffic Manager. Then, click the ID of the instance that you want to manage. On the global configurations page, Click the Alert Logs tab.

22