Logs for the probe: ts=2026-11-13T15:58:59.776829563Z caller=main.go:304 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Beginning probe" probe=http timeout_seconds=8 ts=2026-11-13T15:58:59.776955715Z caller=http.go:274 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Resolving target address" ip_protocol=ip4 ts=2026-11-13T15:58:59.778134863Z caller=http.go:274 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Resolved target address" ip="unsupported value type" ts=2026-11-13T15:58:59.778198813Z caller=main.go:119 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Making HTTP request" url=http://10.99.94.27:8083/actuator/health host=report-server-rest.default:8083 ts=2026-11-13T15:58:59.783488312Z caller=main.go:119 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Received HTTP response" status_code=404 ts=2026-11-13T15:58:59.783508377Z caller=main.go:119 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Invalid HTTP response status code" status_code=404 valid_status_codes="[200 201 204 301 302 303 307 308 401 403]" ts=2026-11-13T15:58:59.783787853Z caller=main.go:119 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-11-13T15:58:59.778271639Z dnsDone=2026-11-13T15:58:59.778271639Z connectDone=2026-11-13T15:58:59.778776365Z gotConn=2026-11-13T15:58:59.778792164Z responseStart=2026-11-13T15:58:59.783471201Z end=2026-11-13T15:58:59.783684936Z ts=2026-11-13T15:58:59.783926275Z caller=main.go:304 module=http_2xx target=http://report-server-rest.default:8083/actuator/health level=error msg="Probe failed" duration_seconds=0.007044217 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.001214831 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 0.007044217 # 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 -1 # 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.000520523 probe_http_duration_seconds{phase="processing"} 0.004679046 probe_http_duration_seconds{phase="resolve"} 0.001214831 probe_http_duration_seconds{phase="tls"} 0 probe_http_duration_seconds{phase="transfer"} 0.000213732 # 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 404 # 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 0 Module configuration: prober: http timeout: 8s http: valid_status_codes: - 200 - 201 - 204 - 301 - 302 - 303 - 307 - 308 - 401 - 403 valid_http_versions: - HTTP/1.1 - HTTP/2 preferred_ip_protocol: ip4 ip_protocol_fallback: true no_follow_redirects: true tcp: ip_protocol_fallback: true icmp: ip_protocol_fallback: true dns: ip_protocol_fallback: true