UptimeHunt Docs
Getting Started

Creating Your First Monitoring Service

Step-by-step guide to configuring HTTP and PING monitoring on UptimeHunt.

Creating Your First Monitoring Service

This tutorial guides you through creating your first monitoring service on UptimeHunt. We'll cover both HTTP and PING monitoring configuration with practical examples.

Before You Begin

Ensure you have:

  • An active UptimeHunt account
  • A website or server to monitor
  • Basic understanding of your service's requirements (URL, IP address, etc.)

Creating an HTTP Monitoring Service

Step 1: Access Service Creation

  1. Log in to your UptimeHunt dashboard
  2. Navigate to the Services page (default view after login)
  3. Click the "Add Service" button in the upper right corner

Step 2: Select Service Type

  1. A modal dialog will appear with available monitoring types
  2. Select "HTTP" for website and API endpoint monitoring
  3. Click on the HTTP option to proceed

Step 3: Configure Basic Settings

Complete the following fields in the service configuration form:

Service Name (Required) — A descriptive name for easy identification. Example: Production API, Company Website, Status Page

Project (Optional) — Assign to an existing project for organizational purposes. Leave unassigned if not using project organization.

Enabled (Toggle) — Set to enabled (ON) to begin monitoring immediately. Disable to configure without starting checks.

Check Interval (Required) — Monitoring frequency in seconds. Default: 180 s (3 min). Minimum depends on plan: Free: 300 s, Pro: 60 s, Team: 30 s, Enterprise: 10 s.

Step 4: Configure HTTP Settings

URL (Required) — Complete URL including protocol. Example: https://api.example.com/health. Supports both HTTP and HTTPS protocols.

HTTP Method (Required) — Request method to use. Options: GET, POST, HEAD. Default: GET. Select POST for endpoints requiring request bodies.

Step 5: Configure Authentication (Optional)

If your endpoint requires authentication, select the appropriate type:

No Authentication — Default setting for public endpoints.

Basic Authentication — For HTTP Basic Auth: select "Basic", enter Username and Password.

Bearer Token — For token-based authentication: select "Bearer Token", enter your token.

Step 6: Add Custom Headers (Optional)

  1. Click "Add Header" button
  2. Enter Header Name (e.g., Accept)
  3. Enter Header Value (e.g., application/json)
  4. Repeat for additional headers

Step 7: Configure POST Data (Optional)

For POST requests, enter request body directly in the text input. Supports JSON, XML, or form data.

Step 8: Save Service

Click "Create Service" to save your configuration. The service will appear in your Services list and monitoring will begin according to your specified interval.

Creating a PING Monitoring Service

Step 1: Access Service Creation

  1. Navigate to Services dashboard
  2. Click "Add Service"

Step 2: Select PING Type

Select "PING" from the monitoring type options.

Step 3: Configure PING Settings

Service Name (Required) — Descriptive identifier for the service.

Project (Optional) — Assign to project for organization.

Enabled (Toggle) — Activate monitoring immediately.

Check Interval (Required) — Frequency in seconds (default: 180).

IP Address / Domain (Required) — Target for ping monitoring. Supports:

  • IPv4 addresses (e.g., 192.168.1.1)
  • IPv6 addresses (e.g., 2001:db8::1)
  • Domain names (e.g., example.com)

Step 4: Save Configuration

Click "Create Service" to activate your PING monitoring.

Verifying Your Service

After creating a service:

  1. Return to the Services dashboard
  2. Locate your new service in the list
  3. Verify the service status shows as "Enabled"
  4. Wait for the first check interval to complete
  5. Click the service name to view details

Example Configurations

Simple Website Monitoring

Service Name: Company Homepage
Type: HTTP
URL: https://www.example.com
Method: GET
Authentication: None
Interval: 300 s (5 min)

API Health Check

Service Name: API Health Endpoint
Type: HTTP
URL: https://api.example.com/v1/health
Method: GET
Authentication: Bearer Token
Token: eyJhbGc...
Headers:
  - Accept: application/json
Interval: 180 s (3 min)

Server Ping Monitoring

Service Name: Production Server
Type: PING
IP Address: 192.168.1.100
Interval: 60 s (1 min)   # requires Pro plan or higher

Best Practices

Naming Conventions

Use clear, descriptive names that indicate environment (Production/Staging), service type (API/Website/Server), and purpose (Health Check/Login/Database).

Select check intervals based on criticality:

  • Critical services: 30–180 s (Team/Enterprise plans enable sub-minute checks)
  • Standard monitoring: 180–600 s
  • Non-critical services: 900–1800 s

Authentication Security

Use dedicated monitoring credentials with read-only permissions where possible. Rotate tokens regularly and never share credentials across services.

Troubleshooting

Service Not Appearing — Refresh the page, check for error messages in the browser console, and verify all required fields were completed.

No Check Results — Verify the service is enabled, wait for the configured interval period, check URL/IP address is accessible from the internet, and review firewall and security settings.

Authentication Failures — Verify credentials are correct, check token expiration, ensure authentication type matches endpoint requirements, and test credentials independently.

Next Steps

On this page