Outcome
A website monitor is active and running scheduled checks against a real URL, and you have seen its first result.
Before you start
- You need the
monitors:managepermission (Owner, Admin, or Member). - Use a public HTTPS endpoint. Fajita cannot reach private networks or
localhost.
Steps
Open the new monitor wizard
Go to Monitors, then New monitor, and choose Website.
Enter the URL
Use the full address, including the scheme.
https://example.com/healthSet the check interval
Choose how often Fajita checks. Intervals run from every minute to every hour. A faster interval detects problems sooner and uses more of your check volume.
Test before you save
Run a manual test. Fajita performs one real check and shows the response, timing, and whether each assertion passed. Fix anything red before saving.
Activate
Save and activate the monitor. It moves from
drafttoactiveand begins its schedule.
Verify the setup
- Wait for the first scheduled check to complete.
- Open the monitor's history and confirm a
successresult appears. - Confirm the response time and status code match what you expect.
What happens next
Connect a channel so a confirmed failure reaches you: Connect an alert channel.
Common problems
- Destination blocked: the URL resolves to a private address. See Why was my check blocked?.
- Unexpected status: confirm the endpoint returns a success code without authentication, or add an auth header.