http_check — HTTP(S) checks with TLS expiry¶

Free tier. Checks a list of URLs every cycle: status validation, latency broken down by phase (DNS, connect, TLS handshake, time-to-first-byte, total), response size, optional content matching — and the remaining validity of the TLS certificate as a first-class metric.

Quick start¶

# probes.d/30-web.yaml
- name: web-checks
  type: http_check
  params:
    targets:
      - "https://www.example.com"
      - "https://api.example.com/healthz"
    interval: 60

Parameters¶

Parameter	Default	Description
`targets`	required	List of URLs to check
`method`	GET	HTTP method
`timeout`	10	Per-target budget in seconds
`interval`	60	Seconds between cycles
`expected_status`	any 2xx/3xx	Exact status code that counts as up
`content_match`	none	Regexp the response body must match for the check to be up
`insecure_skip_verify`	false	Accept self-signed certificates (labs)

Targets are checked in parallel (bounded). Redirects are reported, not followed: a 301 is the measured answer of the target.

Metrics¶

One series per metric per target (target tag).

Metric	Unit	Description
`senhub.httpcheck.up`	bool	Expected status (and content, if configured)
`senhub.httpcheck.status.code`	code	Last response status
`httpcheck.duration`	ms	Total request time
`senhub.httpcheck.duration.dns` / `.connect` / `.tls` / `.ttfb`	ms	Phase breakdown
`senhub.httpcheck.response.size`	B	Body size (1 MiB read cap)
`senhub.httpcheck.tls.expiry`	days	Days until the certificate expires — negative once expired. Alert under 30
`senhub.httpcheck.content.match`	bool	Only when `content_match` is configured

A failing or unreachable target is a measurement (up = 0), never a probe failure.