Website monitoring

Outcome

A website monitor checks a public URL on a schedule and verifies the response before opening an incident.

Supported URLs

• https:// and http:// schemes. Prefer HTTPS.
• Publicly resolvable hostnames only. Private addresses and localhost are blocked for safety.

https://example.com
https://app.example.com/health

Request methods

Website monitors use GET or HEAD. Use an API monitor when you need POST or a request body.

What Fajita checks

• The request completed without a transport error.
• The status code is one you expect (a success code by default).
• The response time is under your threshold, if set.
• Any keyword assertions passed. See Keyword assertions.

Redirects

Fajita follows redirects to a public destination. A redirect to a private or restricted address is treated as a blocked destination, not a success.

Intervals and retries

Choose an interval from every minute to every hour. A failed request is retried before verification begins. See Check intervals and Retries.

Pausing and archiving

Pause a monitor to stop checks without losing configuration. Archive it to retire it while keeping its history. See Monitor states.