Getting Started
This guide walks you through everything you need to know to go from a fresh account to a fully monitored service with alerts firing correctly — no prior monitoring experience required.
On this page
Monitorion is a professional-grade uptime and infrastructure monitoring platform. It continuously checks your websites, APIs, servers, DNS records, SSL certificates, and domain registrations from multiple locations around the world — and notifies you the instant something goes wrong.
Whether you are a solo developer wanting to know when your side project goes down, or an agency managing dozens of client sites, Monitorion scales to fit. It replaces the patchwork of cron jobs, ping scripts, and manual SSL checks with a single, polished dashboard.
Checks run every 1–5 minutes, 24 hours a day, from global probe locations.
Get notified by email, SMS, webhook, Telegram, or PagerDuty — your choice.
Share a branded status page with your customers to reduce support load.
Monitorion offers two sign-up methods. Both are free and take less than 30 seconds.
Navigate to monitorion.com/signup in your browser.
You can register with:
Check your inbox for a message from [email protected]. Click the verification link. If it does not arrive within a minute, check your spam folder or use the "Resend verification" link on the login page.
After verification you are redirected to your dashboard. It is empty for now — the next section shows you how to add your first monitor.
An HTTP monitor is the most common type and a great place to start. It checks whether a URL returns the expected HTTP status code and, optionally, whether the response body contains a specific keyword. Follow the steps below to add one.
On your dashboard, click the + Add monitor button in the top-right corner. A modal opens prompting you to choose a monitor type.
Choose the HTTP / Website tile. The form expands to show all available configuration fields.
Here is what each field means:
| Field | Description |
|---|---|
Namerequired | A human-friendly label for the monitor, e.g. Production API — /health. Shown in alerts and on the dashboard. |
URLrequired | The full URL to check, including the scheme. Example: https://api.example.com/health. HTTP and HTTPS are both supported. |
Check interval | How often to run the check. Free plan: every 5 minutes. Pro plan: as low as 1 minute. Business plan: 30 seconds. |
HTTP method | The HTTP verb to use. Defaults to GET. Use HEAD for a lighter-weight ping, or POST when the endpoint requires a request body. |
Expected status code | The HTTP status code that signals the service is healthy. Defaults to 200. You can set any valid code, e.g. 201, 301, 204. |
Keyword match | An optional string that must appear in the response body. If the keyword is absent, the check is treated as a failure even if the status code is correct. Useful for detecting blank pages or maintenance mode screens. |
Request timeout | Maximum time (in seconds) to wait for a response before the check is recorded as a Timeout. Default: 30 s. Reduce this for fast APIs; increase for slow batch endpoints. |
Custom headers | Optional HTTP headers sent with every request, e.g. Authorization: Bearer token. Useful for authenticated health endpoints. |
Regions | Pro plan feature. Select one or more geographic probe regions to run checks from (US East, EU West, AP Southeast). A site is considered down only when multiple regions agree. |
Click Create monitor. Monitorion runs the first check immediately. Within a few seconds, the monitor card on your dashboard will show a Up or Down status badge. The response time (in ms) is also displayed.
https://api.example.com/health, Method: GET, Expected status: 200, Keyword: {"status":"ok"}. This ensures both the server is reachable and the application itself reports healthy.You can also create monitors via the REST API if you prefer infrastructure-as-code:
bash — create an HTTP monitor via API
curl -X POST https://app.monitorion.com/api/v1/monitors \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"monitor_type": "http",
"name": "Production Homepage",
"config": {
"url": "https://example.com",
"expectedStatusCode": 200,
"keyword": "Welcome"
},
"interval_seconds": 300
}'A monitor without alerts is a tree falling in an empty forest. Monitorion automatically sends you an email when any monitor goes down, using the address you registered with. Here is how to verify that, and how to add additional channels.
Navigate to Settings → Alert Channels. You will see an email channel pre-configured with your registration address. It is enabled by default. You can update the address, add a display name, or disable the channel from this screen.
Pro and Business subscribers can add multiple alert channels per project. Click Add channel and choose one of the following:
Receive a text message within seconds of an incident. Each plan includes a monthly SMS allocation (Pro: 50, Business: 200, Agency: 500). Need more? Buy credit bundles (50/$5 · 200/$15 · 500/$30) from Settings → Notifications.
POST a JSON payload to any URL you control — perfect for Slack, Discord, or custom internal tooling. Monitorion signs each request with a shared secret.
Connect a Telegram bot and receive instant messages in any chat or channel. Follow the in-app wizard to link your bot token.
Trigger and resolve PagerDuty incidents automatically. Provide your PagerDuty integration key in the channel settings.
Once a channel exists, open any monitor, click Edit, and scroll to the Alert channels section. Toggle on whichever channels should receive notifications for that specific monitor. A single monitor can fan out to all channels simultaneously.
Every channel has a Send test notification button. Use it after saving to confirm the integration works end-to-end before you rely on it in production.
Each monitor card displays a status badge. Here is what every status means and what action, if any, you should take.
The last check returned the expected status code (and keyword, if configured) within the timeout window. Everything is working normally. No action required.
The check failed — either the server refused the connection, returned an unexpected status code, or the keyword was not found in the response body. An incident is automatically created and your configured alert channels are notified. Investigate immediately.
The server accepted the connection but did not respond within the configured timeout window (default 30 s). This often indicates an overloaded server, a database query that is running too long, or a firewall silently dropping packets. Treated as a failure for alerting and SLA calculation purposes.
The service is reachable and returning the correct status code, but response times are significantly above your baseline. Monitorion flags this automatically when the response time exceeds your configured threshold (Pro plan). Your users may be experiencing slowness. Investigate performance — check database query times, CDN cache hit rates, and server CPU/memory.
Used by SSL certificate and Domain expiration monitors. The certificate or domain is still valid but will expire within your configured warning threshold (default: 30 days, then 14 days, then 7 days). You will receive a reminder alert at each threshold. Take action by renewing the certificate or registering the domain before it lapses.
Checks for this monitor are temporarily suspended. This happens when you manually pause a monitor or when a maintenance window is active. No alerts are sent. The monitor resumes automatically when the maintenance window ends, or when you click "Resume" in the monitor settings.
The dashboard is your command centre. Here is a breakdown of what you will see and how to use each part effectively.
At the top of the dashboard, four counters give you an instant overview: Total monitors, Up, Down, and Paused. A green row means everything is healthy. Any red counter demands immediate attention.
Each monitor is represented as a card showing:
Click any card to open the Monitor Detail view with a full response time chart, the last 50 checks, and incident history.
The detail page contains three tabs:
The global Incidents page (left sidebar) shows all open and resolved incidents across every monitor. Click an incident to add a root cause note, update the status manually, or link it to a public status page update.
Monitorion's free plan is genuinely useful for personal projects and small sites. Below are its boundaries, so you know exactly what you are working with.
| Feature | Free plan | Pro plan |
|---|---|---|
| Monitors | 10 | 50 |
| Monitor types | HTTP, Ping, SSL Certificate, Domain Expiry, Security Headers, Mixed Content | All 25 types |
| Check interval | 5 minutes | 1 minute (30 s on Business) |
| History retention | 7 days | 30 days |
| Alert channels | Email only | All 9 — Email, SMS (50–500/mo), Slack, Discord, Telegram, Teams, Google Chat, Webhook, PagerDuty |
| Multi-region checks | No | Yes (2–3 regions) |
| Public status pages | 1 basic page | Yes (custom branding) |
| Team members | Solo | 5 per project |
| Projects / workspaces | No | Yes |
| SLA reports | No | PDF & CSV export |
| API access | No | Yes |
No credit card required to start. Upgrade at any time.
You now have a running monitor and alerts configured. Here is what to explore next:
Set up SSL, DNS, domain, port, and heartbeat monitors. Each type has its own configuration guide.
Read guide →Deep-dive into webhook payloads, Telegram bot setup, PagerDuty escalation policies, and alert filtering.
Read guide →Create a public status page for your service, add your logo, and let customers subscribe to incident updates.
Read guide →Learn how incidents are created, escalated, and resolved. Add root cause notes and track MTTR over time.
Read guide →Understand how global probe locations work, how consensus is calculated, and when to use multiple regions.
Read guide →Manage monitors, list incidents, and ping heartbeats programmatically with the Monitorion REST API.
Read guide →Free plan. No credit card. Up and running in under two minutes.
Create free accountSomething unclear? Contact support — we typically reply within one business day.