Collection
The portal Node process runs two fixed HTTPS GET probes every 60 seconds with an 8-second deadline and standard TLS certificate verification. Only response headers are measured; response bodies and cookies are discarded. Redirects are not followed and count as unsuccessful, since the monitored URLs are expected to return a successful page directly.
Storage and dashboard
The loopback metrics endpoint exports website_probe_success, website_probe_duration_seconds, website_probe_status_code, website_probe_certificate_expiry_timestamp_seconds and website_probe_last_check_timestamp_seconds. The website label is limited to ramideltoro or showalgo. Existing Alloy scrapes port 4311 once a minute and writes into Grafana Cloud. Public views provide four curated metrics; owner dashboards add time since the last probe.
Interpretation
Rolling-hour availability uses avg_over_time over stored success samples, not an externally measured SLA. HTTP status zero indicates no HTTP response. Missing certificate data is omitted. Historical data accumulates after deployment. A check older than three minutes is unavailable.
Releases
The observability repository owns the probe definitions and dashboard catalog. Its workflow dispatches the infrastructure pipeline, which checks documentation fingerprints and production Qwen compatibility before and after activation.