Logs for the probe: ts=2026-06-29T01:54:03.269776578Z caller=main.go:190 module=http target=https://tenant.carelab.me/login level=info msg="Beginning probe" probe=http timeout_seconds=9.5 ts=2026-06-29T01:54:03.269876278Z caller=http.go:328 module=http target=https://tenant.carelab.me/login level=info msg="Resolving target address" target=tenant.carelab.me ip_protocol=ip6 ts=2026-06-29T01:54:03.350818473Z caller=http.go:328 module=http target=https://tenant.carelab.me/login level=info msg="Resolved target address" target=tenant.carelab.me ip=2600:9000:27af:f000:5:875b:6900:93a1 ts=2026-06-29T01:54:03.350909803Z caller=client.go:259 module=http target=https://tenant.carelab.me/login level=info msg="Making HTTP request" url=https://[2600:9000:27af:f000:5:875b:6900:93a1]/login host=tenant.carelab.me ts=2026-06-29T01:54:12.770711741Z caller=handler.go:119 module=http target=https://tenant.carelab.me/login level=error msg="Error for HTTP request" err="Get \"https://[2600:9000:27af:f000:5:875b:6900:93a1]/login\": context deadline exceeded" ts=2026-06-29T01:54:12.770785921Z caller=handler.go:119 module=http target=https://tenant.carelab.me/login level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-06-29T01:54:03.351026863Z dnsDone=2026-06-29T01:54:03.351026863Z connectDone=2026-06-29T01:54:03.352749183Z gotConn=2026-06-29T01:54:03.356508643Z responseStart=0001-01-01T00:00:00Z tlsStart=2026-06-29T01:54:03.352788523Z tlsDone=2026-06-29T01:54:03.356447063Z end=0001-01-01T00:00:00Z ts=2026-06-29T01:54:12.770825211Z caller=main.go:190 module=http target=https://tenant.carelab.me/login level=error msg="Probe failed" duration_seconds=9.501017473 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.080966465 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 9.501017473 # 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.00172233 probe_http_duration_seconds{phase="processing"} 0 probe_http_duration_seconds{phase="resolve"} 0.080966465 probe_http_duration_seconds{phase="tls"} 0.00365853 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 6.97214065e+08 # HELP probe_ip_protocol Specifies whether probe ip protocol is IP4 or IP6 # TYPE probe_ip_protocol gauge probe_ip_protocol 6 # HELP probe_success Displays whether or not the probe was a success # TYPE probe_success gauge probe_success 0 Module configuration: prober: http timeout: 10s http: valid_status_codes: - 200 - 301 - 302 ip_protocol_fallback: true 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