Monitors, alerts and the reliability report

Tests in CI tell you whether a change broke something. Monitors tell you whether the live API is working right now: they run a collection on a schedule from the Swastik Codes servers and alert you when it fails.

Create a monitor

1. Open Monitors in the left sidebar and click +.
2. Pick the collection and environment to run.
3. Choose how often: every 5 minutes, hourly, daily, or any cron schedule (times are UTC).
4. Add who to tell: email addresses, and a webhook URL. Paste a Slack, Microsoft Teams or Discord incoming-webhook URL and failures arrive as chat messages with the failing tests and a link to the run.
5. Save. Use Run now from the monitor's menu to try it immediately.

Monitors can retry a failed run before alerting, so one network blip does not wake anyone up, and they tell you again when the API recovers.

Read a run

Open a monitor to see its runs. Each run shows every request with its status, time and tests, so you can see which check failed and what the API answered.

The reliability report

Click the chart icon (Reliability report) at the top of the Monitors panel for the whole workspace over the last 7, 30 or 90 days:

• the overall pass rate, failed runs and how many changes were saved;
• monitor runs per day, passed and failed (hover a day for details, or switch to a table);
• each monitor's pass rate, average and slowest run times, and its last failure;
• the requests that fail most, with their last error;
• who changed the workspace most.

Download saves the report as text for a status update or a post-incident review.

What you learned

• Monitors run collections on a schedule and alert by email, webhook, Slack, Teams or Discord.
• The reliability report shows pass rates, failure trends and the requests that fail most.

Next: let your AI coding assistant use your API collection.

Go deeper

• FeatureAPI monitoring
• LessonRun a whole collection
• LessonShare a workspace with your team