Site Sentinel: Your Website Says 200 OK. The Customers Disagree.

Description and use

Site Sentinel is a MatrixSwarm tool that monitors website health by checking HTTP responses, required content, linked assets, TLS certificates, access logs, and host resources, producing structured evidence for incident investigation.

Problem

A website reports 200 OK but customers see maintenance or broken pages, making it hard to detect real availability issues.

Outcome

Site Sentinel provides structured evidence of website health, enabling precise incident investigation without performing remediation actions.

Workflow

• Install MatrixOS on the monitoring host or target server.
• Create a Swarm Workspace and add agents: site_sentinel, forensic_detective, matrix_https, matrix_websocket, log_streamer, and an alert relay.
• Configure Site Sentinel’s public and origin targets with URL, optional origin_url, host_header, expect marker, and note.
• Enable linked asset verification to sample up to 8 (configurable to 25) CSS/JS/image assets.
• Enable traffic analysis by listing access‑log files and setting thresholds for rate, distinct paths, and error ratio.
• Run Site Sentinel to collect evidence; review classifications such as PUBLIC_CONTENT_MISMATCH, PUBLIC_ASSET_FAILURE, ORIGIN_DEGRADED, EDGE_DEGRADED, SITE_UNAVAILABLE, PUBLIC_LATENCY, TLS_EXPIRING.
• Use Forensic Detective to investigate critical incidents and trigger alerts.
• Iterate by adding oracle analysis or adjusting thresholds as needed.

Evidence

MatrixSwarm’s site_sentinel checks the public page, required content, a sample of linked assets, an optional origin endpoint, and certificate lifetime.

Source

Site Sentinel observes and reports. It does not restart Apache, ban addresses, purge caches, repair deployments, or quarantine files.

Source

Enable Verify linked CSS, JavaScript, and images to sample assets referenced directly in the HTML.

Source