PB PulseBeacon Docs
Home / Docs / Keyword Monitoring

Monitoring

Keyword Monitoring

Validate response content with contains / not-contains checks.

Keyword monitors fetch a URL and validate response content. You can alert when content is missing, or alert when unwanted content appears.

Good Fits

Detect maintenance pages, hidden error banners, missing success text, or unexpected incident messages.

Configuration

  • URL (required)
  • Keyword / phrase (required)
  • Match mode: contains or not_contains
  • Case sensitivity: on/off
  • Timeout + interval like other synthetic checks

Examples

Contains (healthy text) 
URL: https://status.example.com/health
Match mode: contains
Keyword: OK
Case-sensitive: false
Not Contains (block undesired text) 
URL: https://www.example.com
Match mode: not_contains
Keyword: Maintenance mode
Case-sensitive: false
Error Banner Detection 
URL: https://app.example.com
Match mode: not_contains
Keyword: Something went wrong

Status + Events

  • HTTP response status still must match expected status rule (default 200-299).
  • A failing keyword condition enters Confirming… first; the monitor is marked down only after consecutive confirmed failures (3 by default), so a one-off CDN error page or timeout never alerts.
  • Recovery to normal condition moves status back to up with a single recovery alert.
  • Type-specific notification events: keyword_missing and keyword_restored.

Avoid False Positives

Use stable strings that only appear when your application is healthy. Avoid volatile values (timestamps, rotating IDs, ad content).