Create your first monitor

In this guide you will create your first HTTP monitor for your website or API step by step. As soon as you save it, ePulz.io starts checking the page and alerts you whenever there is a problem.

Step 1: Open monitor creation

• In the overview, click the + Add monitor button.
• Choose the HTTP/HTTPS type - the most common choice for websites and APIs.

Step 2: Basic details

• Name - any description for your own clarity, for example Main website, API server or E-shop checkout.
• Address (URL) - the full address including https:// (for example https://mycompany.com).
• HTTP method - typically GET (regular page load). Use POST for API endpoints that do not support GET.

Step 3: Check interval

Determines how often ePulz.io tests your address. The shortest interval depends on your plan:

• Trial and Standard: from 5 minutes.
• Pro: from 2 minutes.
• Business: from 1 minute.

For most websites 5 minutes is more than enough. A shorter interval makes sense for critical services where seconds mean money - for example an e-shop checkout or a payment gateway.

Step 4: Expected state

• Status code - which HTTP code the server should return for the response to be considered fine. Default is 200 (page is fine). For redirects set, for example, 301.
• Timeout - the maximum time in seconds after which the check is treated as an outage. Default is 15 seconds.
• Keyword in content (optional) - text that must be present in the response, for example Welcome or <title>Home. It helps detect a so-called silent outage, when the server returns 200 but shows a blank or error page.

Step 5: SSL and domain check

For HTTPS addresses, turn on these two checks:

• SSL check - warns you in advance about the expiring security certificate (30, 14, 7, 3 and 1 day before the end).
• Domain check (WHOIS - public domain name register) - warns you about the upcoming expiry of the domain registration.

Both checks are included, cost nothing extra and can save you real trouble.

Step 6: Notifications

Choose the channels on which you want to receive an alert during an outage:

• E-mail - to your account address, enabled by default.
• Telegram - requires a connected Telegram.
• Webhook - your own address for Slack, Discord or your system.

Step 7: Number of failures before alerting

An optional setting. It determines how many consecutive failed checks must occur before we send an alert. The default value is 1 (alert immediately). Setting it to 2 or 3 reduces the number of false alarms during one-off network fluctuations.

Step 8: Saving the monitor

Click Create monitor. The first check runs within one minute. In the overview you will see the status move from Pending to OK, or possibly Outage.

What happens during an outage

• ePulz.io detects a failed check (wrong status code, exceeded timeout, missing keyword).
• If the number of failures before alerting is set, the check is repeated for verification.
• Optionally, the outage is also verified from another location (from multiple regions) to rule out a local issue.
• We send an alert to all enabled channels.
• We create an incident record with the start time.
• After the first successful check we send a recovery alert including the outage duration.