Logs for the probe: time=2026-04-09T04:36:20.968-06:00 level=INFO source=handler.go:195 msg="Beginning probe" module=http_2xx target=prometheus.io probe=http timeout_seconds=5 time=2026-04-09T04:36:20.996-06:00 level=INFO source=handler.go:195 msg="Resolving target address" module=http_2xx target=prometheus.io target=prometheus.io ip_protocol=ip4 time=2026-04-09T04:36:23.613-06:00 level=INFO source=handler.go:195 msg="Resolved target address" module=http_2xx target=prometheus.io target=prometheus.io ip=172.67.201.240 time=2026-04-09T04:36:23.675-06:00 level=INFO source=handler.go:195 msg="Making HTTP request" module=http_2xx target=prometheus.io url=http://172.67.201.240 host=prometheus.io time=2026-04-09T04:36:25.935-06:00 level=INFO source=handler.go:195 msg="Error for HTTP request" module=http_2xx target=prometheus.io err="Get \"http://172.67.201.240\": context deadline exceeded" time=2026-04-09T04:36:25.935-06:00 level=INFO source=handler.go:195 msg="Response timings for roundtrip" module=http_2xx target=prometheus.io roundtrip=0 start=2026-04-09T04:36:23.688-06:00 dnsDone=2026-04-09T04:36:23.688-06:00 connectDone=2026-04-09T04:36:25.468-06:00 gotConn=2026-04-09T04:36:25.468-06:00 responseStart=0001-01-01T00:00:00.000Z tlsStart=0001-01-01T00:00:00.000Z tlsDone=0001-01-01T00:00:00.000Z end=0001-01-01T00:00:00.000Z time=2026-04-09T04:36:25.935-06:00 level=INFO source=handler.go:195 msg="Probe failed" module=http_2xx target=prometheus.io duration_seconds=4.967329912 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.61634324 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 4.967329912 # 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"} 1.780326657 probe_http_duration_seconds{phase="processing"} 0 probe_http_duration_seconds{phase="resolve"} 2.61634324 probe_http_duration_seconds{phase="tls"} 0 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 1.788760585e+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: 5s http: valid_status_codes: - 200 - 201 - 202 - 203 - 204 - 205 - 206 - 207 - 208 - 226 valid_http_versions: - HTTP/1.1 - HTTP/2.0 preferred_ip_protocol: ip4 method: GET headers: User-Agent: blackbox-monitoring 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