Advanced Monitoring Fields
The four advanced site fields — response-time threshold, HTTP method, custom headers, and expected body — explained with examples.
Advanced Monitoring Fields#
The Advanced Monitoring section on Add Site / Edit Site exposes four fields that let you tune exactly how LemWatch probes your endpoint. All four persist correctly — earlier versions silently dropped them because they were missing from the validation schema. That's fixed.
1. Response time threshold (ms)#
2. HTTP method#
HEAD, GET, POST, PUTHEAD is cheapest; switch to GET if your origin returns 405 on HEAD3. Custom headers#
4. Expected body contains#
Where these live#
Together with the health alert threshold they form the per-site alerting contract. Save the site to apply — changes take effect on the next scheduled check.
Troubleshooting#
{"X-Token":"abc"}), not an array or string.Related Articles
Response Time Threshold Alerts
Get alerted when response times consistently exceed your limits.
Custom HTTP Methods & Headers
Monitor endpoints behind authentication with custom headers.
Custom Request Headers
Send custom HTTP headers with every check — bearer tokens, User-Agents, host overrides. Validated as JSON, 4 kB cap.
Expected Body Content
Assert a substring exists in the response body. 500-char cap. Use for "page renders" checks; for richer rules use Money Page Monitor.
Health Alert Threshold
Set the health-score number that triggers an alert. Range 0–100, default 70. Setting 0 is valid and disables score-based alerts.