Quick Start

This guide walks you through the basics: signing up, creating a monitor, connecting a notification channel, and wiring everything together with an escalation policy.

1. Sign Up

Visit console.yipyap.run/register and create an account. The Free plan includes up to 5 monitors with 5-minute check intervals.

2. Create Your First Monitor

1. Navigate to Monitors in the sidebar.
2. Click New Monitor.
3. Choose HTTP as the check type.
4. Enter the URL you want to monitor (e.g. https://api.example.com/health).
5. Set the check interval to 60 seconds.
6. Set the confirmation threshold to 2 (the monitor must fail twice before firing an alert).
7. Click Save.

Your monitor will begin checking immediately. The dashboard shows real-time status, latency, and uptime percentage.

3. Connect a Notification Channel

1. Go to Settings > Notifications.
2. Click Add Channel.
3. Select your preferred channel type (Slack, Discord, email, etc.).
4. Follow the setup instructions for that channel. For Slack, you will install the YipYap bot app. For email, you will configure SMTP credentials.
5. Send a test notification to confirm delivery.

4. Create an Escalation Policy

1. Navigate to Alerting > Escalation Policies.
2. Click New Policy.
3. Add a first step: select the notification channel you just created.
4. Optionally add a second step with a different channel or user, and set a wait time (e.g. 5 minutes).
5. Enable Loop if you want the policy to repeat until the alert is acknowledged.
6. Click Save.

5. Assign the Policy to Your Monitor

1. Open your monitor’s settings.
2. Under Escalation Policy, select the policy you just created.
3. Save.

That is it. When your endpoint goes down, YipYap will detect the failure, fire an alert, and notify you through your configured channels following the escalation steps you defined.

Tip

You can test your entire alerting pipeline by temporarily changing your monitor’s URL to an endpoint that returns a 500 error. Once the confirmation threshold is reached, the alert fires and you can verify that notifications arrive as expected.

What to Explore Next

• Monitor types for TCP, DNS, Ping, and Heartbeat checks
• On-call schedules for rotating who receives alerts
• Status pages for sharing uptime with your users