Logs for the probe:
ts=2026-04-18T03:40:54.948173659Z caller=main.go:190 module=http_2xx target=https://dev.dskk.1bit.support level=info msg="Beginning probe" probe=http timeout_seconds=9.5
ts=2026-04-18T03:40:54.948238099Z caller=http.go:328 module=http_2xx target=https://dev.dskk.1bit.support level=info msg="Resolving target address" target=dev.dskk.1bit.support ip_protocol=ip4
ts=2026-04-18T03:40:54.948286878Z caller=http.go:328 module=http_2xx target=https://dev.dskk.1bit.support level=info msg="Resolved target address" target=dev.dskk.1bit.support ip=10.96.102.3
ts=2026-04-18T03:40:54.94833867Z caller=client.go:259 module=http_2xx target=https://dev.dskk.1bit.support level=info msg="Making HTTP request" url=https://10.96.102.3 host=dev.dskk.1bit.support
ts=2026-04-18T03:41:04.449094843Z caller=handler.go:119 module=http_2xx target=https://dev.dskk.1bit.support level=error msg="Error for HTTP request" err="Get \"https://10.96.102.3\": context deadline exceeded"
ts=2026-04-18T03:41:04.449142563Z caller=handler.go:119 module=http_2xx target=https://dev.dskk.1bit.support level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-04-18T06:40:54.948393108+03:00 dnsDone=2026-04-18T06:40:54.948393108+03:00 connectDone=2026-04-18T06:40:54.948546271+03:00 gotConn=2026-04-18T06:40:54.949727391+03:00 responseStart=0001-01-01T00:00:00Z tlsStart=2026-04-18T06:40:54.948563167+03:00 tlsDone=2026-04-18T06:40:54.949695268+03:00 end=0001-01-01T00:00:00Z
ts=2026-04-18T03:41:04.449162339Z caller=main.go:190 module=http_2xx target=https://dev.dskk.1bit.support level=error msg="Probe failed" duration_seconds=9.500966847



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 4.7795e-05
# HELP probe_duration_seconds Returns how long the probe took to complete in seconds
# TYPE probe_duration_seconds gauge
probe_duration_seconds 9.500966847
# 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.000153161
probe_http_duration_seconds{phase="processing"} 0
probe_http_duration_seconds{phase="resolve"} 4.7795e-05
probe_http_duration_seconds{phase="tls"} 0.001132101
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 3.931702928e+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
http:
  preferred_ip_protocol: ip4
  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