Logs for the probe: ts=2026-03-27T12:00:08.344303544Z caller=main.go:190 module=http_2xx target=https://healthbeat.intercare.co.za level=info msg="Beginning probe" probe=http timeout_seconds=9.5 ts=2026-03-27T12:00:08.344426657Z caller=http.go:328 module=http_2xx target=https://healthbeat.intercare.co.za level=info msg="Resolving target address" target=healthbeat.intercare.co.za ip_protocol=ip4 ts=2026-03-27T12:00:08.345275551Z caller=http.go:328 module=http_2xx target=https://healthbeat.intercare.co.za level=info msg="Resolved target address" target=healthbeat.intercare.co.za ip=104.26.15.102 ts=2026-03-27T12:00:08.345330853Z caller=client.go:259 module=http_2xx target=https://healthbeat.intercare.co.za level=info msg="Making HTTP request" url=https://104.26.15.102 host=healthbeat.intercare.co.za ts=2026-03-27T12:00:17.84749518Z caller=handler.go:119 module=http_2xx target=https://healthbeat.intercare.co.za level=error msg="Error for HTTP request" err="Get \"https://104.26.15.102\": context deadline exceeded" ts=2026-03-27T12:00:17.847541161Z caller=handler.go:119 module=http_2xx target=https://healthbeat.intercare.co.za level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-03-27T12:00:08.345394344Z dnsDone=2026-03-27T12:00:08.345394344Z connectDone=2026-03-27T12:00:08.36707166Z gotConn=2026-03-27T12:00:08.393414349Z responseStart=0001-01-01T00:00:00Z tlsStart=2026-03-27T12:00:08.367091261Z tlsDone=2026-03-27T12:00:08.393342257Z end=0001-01-01T00:00:00Z ts=2026-03-27T12:00:17.847563182Z caller=main.go:190 module=http_2xx target=https://healthbeat.intercare.co.za level=error msg="Probe failed" duration_seconds=9.503225918 Metrics that would have been returned: # HELP probe_dns_lookup_time_seconds Returns the time taken for probe dns lookup in seconds # TYPE probe_dns_lookup_time_seconds gauge probe_dns_lookup_time_seconds 0.000851835 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 9.503225918 # HELP probe_failed_due_to_regex Indicates if probe failed due to regex # TYPE probe_failed_due_to_regex gauge probe_failed_due_to_regex 0 # HELP probe_http_content_length Length of http content response # TYPE probe_http_content_length gauge probe_http_content_length 0 # HELP probe_http_duration_seconds Duration of http request by phase, summed over all redirects # TYPE probe_http_duration_seconds gauge probe_http_duration_seconds{phase="connect"} 0.021677316 probe_http_duration_seconds{phase="processing"} 0 probe_http_duration_seconds{phase="resolve"} 0.000851835 probe_http_duration_seconds{phase="tls"} 0.026251006 probe_http_duration_seconds{phase="transfer"} 0 # HELP probe_http_redirects The number of redirects # TYPE probe_http_redirects gauge probe_http_redirects 0 # HELP probe_http_ssl Indicates if SSL was used for the final redirect # TYPE probe_http_ssl gauge probe_http_ssl 0 # HELP probe_http_status_code Response HTTP status code # TYPE probe_http_status_code gauge probe_http_status_code 0 # HELP probe_http_uncompressed_body_length Length of uncompressed response body # TYPE probe_http_uncompressed_body_length gauge probe_http_uncompressed_body_length 0 # HELP probe_http_version Returns the version of HTTP of the probe response # TYPE probe_http_version gauge probe_http_version 0 # HELP probe_ip_addr_hash Specifies the hash of IP address. It's useful to detect if the IP address changes. # TYPE probe_ip_addr_hash gauge probe_ip_addr_hash 2.658123978e+09 # HELP probe_ip_protocol Specifies whether probe ip protocol is IP4 or IP6 # TYPE probe_ip_protocol gauge probe_ip_protocol 4 # HELP probe_success Displays whether or not the probe was a success # TYPE probe_success gauge probe_success 0 Module configuration: prober: http timeout: 15s http: valid_http_versions: - HTTP/1.1 - HTTP/2.0 preferred_ip_protocol: ip4 fail_if_not_ssl: true method: GET follow_redirects: true enable_http2: true tcp: ip_protocol_fallback: true icmp: ip_protocol_fallback: true ttl: 64 dns: ip_protocol_fallback: true recursion_desired: true