Logs for the probe: ts=2026-11-19T00:49:45.47005543Z caller=main.go:118 module=http target=http://127.0.0.1:9104/ level=info msg="Beginning probe" probe=http timeout_seconds=9.5 ts=2026-11-19T00:49:45.470156208Z caller=utils.go:42 module=http target=http://127.0.0.1:9104/ level=info msg="Resolving target address" preferred_ip_protocol=ip6 ts=2026-11-19T00:49:45.470172812Z caller=utils.go:52 module=http target=http://127.0.0.1:9104/ level=warn msg="Resolution with preferred IP protocol failed, attempting fallback protocol" fallback_protocol=ip4 err="address 127.0.0.1: no suitable address found" ts=2026-11-19T00:49:45.470187057Z caller=utils.go:65 module=http target=http://127.0.0.1:9104/ level=info msg="Resolved target address" ip=127.0.0.1 ts=2026-11-19T00:49:45.470205866Z caller=http.go:281 module=http target=http://127.0.0.1:9104/ level=info msg="Making HTTP request" url=http://127.0.0.1:9104/ host=127.0.0.1:9104 ts=2026-11-19T00:49:45.470749681Z caller=http.go:300 module=http target=http://127.0.0.1:9104/ level=info msg="Received HTTP response" status_code=200 ts=2026-11-19T00:49:45.47081768Z caller=http.go:367 module=http target=http://127.0.0.1:9104/ level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-11-19T07:49:45.470264873+07:00 dnsDone=2026-11-19T07:49:45.470264873+07:00 connectDone=2026-11-19T07:49:45.470345971+07:00 gotConn=2026-11-19T07:49:45.470351728+07:00 responseStart=2026-11-19T07:49:45.470725646+07:00 end=2026-11-19T07:49:45.470813125+07:00 ts=2026-11-19T00:49:45.470843887Z caller=main.go:129 module=http target=http://127.0.0.1:9104/ level=info msg="Probe succeeded" duration_seconds=0.00075191 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 2.8095e-05 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 0.00075191 # 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 137 # 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"} 8.6856e-05 probe_http_duration_seconds{phase="processing"} 0.000373917 probe_http_duration_seconds{phase="resolve"} 2.8095e-05 probe_http_duration_seconds{phase="tls"} 0 probe_http_duration_seconds{phase="transfer"} 8.7478e-05 # 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 200 # HELP probe_http_version Returns the version of HTTP of the probe response # TYPE probe_http_version gauge probe_http_version 1.1 # 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 1 Module configuration: prober: http http: valid_status_codes: - 100 - 200 - 201 - 202 - 203 - 204 - 205 - 206 - 207 - 208 - 226 - 300 - 301 - 302 - 303 - 304 - 305 - 306 - 307 - 308 - 400 - 401 - 403 - 404 - 500 - 503 no_follow_redirects: true