Logs for the probe:
time=2025-10-20T20:04:46.481Z level=INFO source=handler.go:122 msg="Beginning probe" module=http_2xx target=https://vision.maximumtest.ru/api/health probe=http timeout_seconds=29.5
time=2025-10-20T20:04:46.481Z level=INFO source=utils.go:61 msg="Resolving target address" module=http_2xx target=https://vision.maximumtest.ru/api/health target=vision.maximumtest.ru ip_protocol=ip6
time=2025-10-20T20:04:46.521Z level=INFO source=utils.go:130 msg="Resolved target address" module=http_2xx target=https://vision.maximumtest.ru/api/health target=vision.maximumtest.ru ip=178.248.235.24
time=2025-10-20T20:04:46.521Z level=INFO source=http.go:153 msg="Making HTTP request" module=http_2xx target=https://vision.maximumtest.ru/api/health url=https://178.248.235.24/api/health host=vision.maximumtest.ru
time=2025-10-20T20:05:15.983Z level=ERROR source=http.go:474 msg="Error for HTTP request" module=http_2xx target=https://vision.maximumtest.ru/api/health err="Get \"https://178.248.235.24/api/health\": context deadline exceeded"
time=2025-10-20T20:05:15.983Z level=INFO source=http.go:601 msg="Response timings for roundtrip" module=http_2xx target=https://vision.maximumtest.ru/api/health roundtrip=0 start=2025-10-20T20:04:46.521Z dnsDone=2025-10-20T20:04:46.521Z connectDone=2025-10-20T20:04:46.530Z gotConn=2025-10-20T20:04:46.542Z responseStart=0001-01-01T00:00:00.000Z tlsStart=2025-10-20T20:04:46.530Z tlsDone=2025-10-20T20:04:46.542Z end=0001-01-01T00:00:00.000Z
time=2025-10-20T20:05:15.983Z level=ERROR source=handler.go:135 msg="Probe failed" module=http_2xx target=https://vision.maximumtest.ru/api/health duration_seconds=29.502379054



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.039476928
# HELP probe_duration_seconds Returns how long the probe took to complete in seconds
# TYPE probe_duration_seconds gauge
probe_duration_seconds 29.502379054
# 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.008928191
probe_http_duration_seconds{phase="processing"} 0
probe_http_duration_seconds{phase="resolve"} 0.039476928
probe_http_duration_seconds{phase="tls"} 0.011729997
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.952620164e+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: 30s
http:
  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