Getting Started

This guide will help you set up your first health check in SysTeam HealthChecks. You'll learn how to create checks, configure notifications, and monitor your services.

1. Create an Account

Start by creating an account at the registration page. After registration, log in to access the dashboard.

2. Create Your First Check

From the dashboard, click the "+ New Check" button to create a new check.

Example: HTTP Check Configuration

Name:My Website

Type:uptime (HTTP)

URL:https://example.com

Interval:60 seconds

Grace Period:60 seconds

Check Type Selection

Choose the appropriate check type based on what you want to monitor:

Type	Use Case
`uptime`	HTTP/HTTPS websites and APIs
`icmp`	Server availability (ping)
`tcp`	TCP port availability
`udp`	UDP services (e.g., NTP)
`dns`	DNS record monitoring
`ftp`	FTP/SFTP server checks
`database`	PostgreSQL, MySQL, MongoDB, Redis
`mail_server`	SMTP, IMAP, POP3 with security scoring
`heartbeat`	Cron jobs and scheduled tasks

3. Configure Notifications

Go to Notifications in the sidebar to set up alert channels. SysTeam supports 10 notification channel types:

Email — HTML email alerts with incident details
Slack — Webhook integration for Slack channels
Discord — Webhook integration for Discord servers
Microsoft Teams — Webhook via Workflows / Power Automate
Telegram — Bot notifications to Telegram chats
Webhook — Custom HTTP endpoint with HMAC signing
PagerDuty — Incident management (Events API v2)
OpsGenie — Alert management (Alert API v2)
Jira — Automatic issue creation on incidents
WhatsApp — Via Meta Business Cloud API

Test Your Notifications

After creating a notification channel, use the Test button to verify it's working correctly before relying on it for alerts.

4. Understanding Check Status

Each check can have one of the following statuses:

UP — Service is operational

DOWN — Service is not responding

DEGRADED — Partial failure (some geo locations down)

LATE — Heartbeat not received on time

NEW — Not yet checked

PAUSED — Monitoring disabled

5. Interval and Grace Period

Configure how often checks run and how long to wait before alerting:

Interval — How often the check runs (e.g., every 60 seconds). Minimum interval depends on your organization's plan.
Grace Period — Wait time before marking a check as DOWN. This prevents false alerts from temporary network issues.

Recommended Settings

For production services, we recommend:
• Interval: 60-300 seconds
• Grace Period: Equal to or greater than the interval

6. Optional: Geo Monitoring

For public-facing services, enable Geo Monitoring to check your service from 8 locations across Europe and the US. This gives you regional performance visibility and detects outages that affect specific geographic areas.

See Agents & Geo Monitoring for details.

7. Optional: Private Agent

Need to monitor internal services behind a firewall? Deploy a private agent inside your network. The agent connects to HealthChecks and runs checks from within your infrastructure.

See Private Agents for setup instructions.

Next Steps

Now that you have a basic check running, explore more features: