Create your first monitor

Goal: Create your first HTTP monitor for your website or API. After creation, ePulz.io starts checking the page and alerts you on an outage.

Step 1: Open monitor creation

1. In the dashboard click + New monitor
2. Select the type HTTP/HTTPS (the most common)

Step 2: Basic details

• Name - any description, e.g. "Main website", "API server", "E-shop checkout"
• URL - the full address including https:// (e.g. https://mycompany.com)
• HTTP method - typically GET. POST for API endpoints that do not support GET.

Step 3: Check interval

How often ePulz.io should check your URL. Depends on your plan:

• Trial / Standard: minimum 5 minutes
• Pro: from 2 minutes
• Business: from 1 minute

For most websites 5 minutes is sufficient. A shorter interval makes sense for business-critical services (e-shop, payment).

Step 4: Expected state

• Status code - which HTTP code should be returned as "OK". Default 200. For redirect endpoints possibly 301.
• Timeout - max time in seconds before the monitor considers it an outage. Default 15 s.
• Keyword in content (optional) - text that must be in the HTML response. E.g. Welcome or <title>Home. Detects "white outage" when the server returns 200 but an empty / error page.

Step 5: SSL and domain check

For an HTTPS URL enable:

• SSL check - alert on certificate expiration (30, 14, 7, 3, 1 day in advance)
• Domain check (WHOIS) - alert on the approaching expiration of the domain registration

Both are free and highly recommended.

Step 6: Notifications

Select which channels should receive an alert on an outage:

• E-mail - to the account e-mail (default on)
• Telegram - requires a linked bot
• Webhook - Slack, Discord, custom endpoint

Step 7: Notify after failures

Optional: send an alert only after N consecutive failures. Default is 1 (immediate alert), but 2 reduces false-positives.

Step 8: Save

Click Create monitor. The first check runs within a minute. In the Dashboard you will see the state move from Pending to OK or Down.

What happens during an outage

1. ePulz.io detects a failed check (bad status, timeout, keyword missing)
2. Checks again (anti-false-positive) - if you have notify after failures set
3. Sends an alert to all enabled channels
4. Creates an incident record with the start timestamp
5. On the next successful check it sends a "recovery" alert with the outage duration