Heartbeat-elastic site monitoring error (Web down)

Elastic Stack Beats
1

Error Msg:
Head https://xx.org/: dial tcp 202.xx.xx.xx:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

May I know does anyone faced this before? Which part has caused this issue? Is it Uptime service / configuration itself or is it on the application we are monitoring?

Thanks ~

2

This error means that the endpoint you're trying to reach did not respond. That could be due to any number of issues. Either network related, permissions related, or software related.

3

Hi so far we have found that there is some connection issue that causes this due to hopping from servers to server. Currently the default heartbeat is listening to a server.

Internal server (Public IP) connecting to GoDaddy server and this does not capture even the site is online.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.