Logs for the probe: ts=2026-07-24T19:59:17.158948706Z caller=main.go:190 module=http_2xx target=prober.mecsys.com.br:443 level=info msg="Beginning probe" probe=http timeout_seconds=5 ts=2026-07-24T19:59:17.159116632Z caller=http.go:328 module=http_2xx target=prober.mecsys.com.br:443 level=info msg="Resolving target address" target=prober.mecsys.com.br ip_protocol=ip4 ts=2026-07-24T19:59:17.455160632Z caller=http.go:328 module=http_2xx target=prober.mecsys.com.br:443 level=info msg="Resolved target address" target=prober.mecsys.com.br ip=170.83.142.148 ts=2026-07-24T19:59:17.455347447Z caller=client.go:259 module=http_2xx target=prober.mecsys.com.br:443 level=info msg="Making HTTP request" url=http://170.83.142.148:443 host=prober.mecsys.com.br:443 ts=2026-07-24T19:59:17.486944761Z caller=handler.go:119 module=http_2xx target=prober.mecsys.com.br:443 level=error msg="Error for HTTP request" err="Get \"http://170.83.142.148:443\": read tcp 10.1.145.184:33968->170.83.142.148:443: read: connection reset by peer" ts=2026-07-24T19:59:17.487005743Z caller=handler.go:119 module=http_2xx target=prober.mecsys.com.br:443 level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-07-24T19:59:17.455501021Z dnsDone=2026-07-24T19:59:17.455501021Z connectDone=2026-07-24T19:59:17.485074706Z gotConn=2026-07-24T19:59:17.485116872Z responseStart=0001-01-01T00:00:00Z tlsStart=0001-01-01T00:00:00Z tlsDone=0001-01-01T00:00:00Z end=0001-01-01T00:00:00Z ts=2026-07-24T19:59:17.48703965Z caller=main.go:190 module=http_2xx target=prober.mecsys.com.br:443 level=error msg="Probe failed" duration_seconds=0.32803037 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.296093222 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 0.32803037 # 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.029615851 probe_http_duration_seconds{phase="processing"} 0 probe_http_duration_seconds{phase="resolve"} 0.296093222 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 2.27822888e+08 # 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_http_versions: - HTTP/1.1 - HTTP/2.0 preferred_ip_protocol: ip4 fail_if_not_ssl: 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