Skip to content

v0.3.0 - Keyword Assertions

Latest
Latest

Choose a tag to compare

View all tags
@venelinkochev venelinkochev released this 22 Aug 11:42
v0.3.0
3b3d618
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.3.0 - Keyword Assertions

HTTP monitors can now assert on the response body, catching the classic "HTTP 200 but the page is broken" false negative.

New: keyword assertions on HTTP monitors (#54)

  • A monitor can require the response body to contain a keyword (great for health endpoints returning "status":"ok") or to not contain one (catch Fatal error or stack traces on a 200 page)
  • Configured per monitor in the Create/Edit forms; the active assertion is shown on the monitor page
  • A failed assertion marks the check down with a readable reason (e.g. Keyword "healthy" not found in response body) and flows through the existing quorum, incident, and notification pipeline
  • Evaluated in the probe against the first 1 MB of the body (case-sensitive), so response bodies never travel through Redis

Upgrading

git pull
./setup.sh --upgrade

Update remote probes to probe-node v0.3.0 to activate assertion evaluation. Older probes keep monitoring normally but ignore assertions and evaluate only the status code — see UPGRADING.md.

Assets 2
Loading