Monitoring

    Advanced Monitoring Fields

    The four advanced site fields — response-time threshold, HTTP method, custom headers, and expected body — explained with examples.

    Updated 2026-06-15
    2 min read
    advanced
    http method
    headers

    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)#

  1. Whole number, 0 – 60,000
  2. Triggers a "slow response" alert when a check exceeds it
  3. Leave blank for the platform default — see Response-time thresholds
  4. 2. HTTP method#

  5. One of: HEAD, GET, POST, PUT
  6. Default HEAD is cheapest; switch to GET if your origin returns 405 on HEAD
  7. See Custom HTTP methods
  8. 3. Custom headers#

  9. JSON object string, max 4,000 characters
  10. Validated as a real JSON object on save — pasted strings are parsed before write
  11. Use for bearer tokens, custom User-Agents, host overrides
  12. Full guide: Custom request headers
  13. 4. Expected body contains#

  14. Up to 500 characters of plain text
  15. Treated as a substring match against the response body
  16. Fires a "content missing" alert when the substring is absent
  17. Full guide: Expected body content
  18. 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#

  19. Field reverts to blank after save? Older builds had this bug; pull the latest and retry.
  20. Headers rejected? The JSON must parse as an object (e.g. {"X-Token":"abc"}), not an array or string.
  21. Was this article helpful?