Services Management

Overview

This guide covers comprehensive service management operations including creating, editing, deleting, and organizing monitoring services within UptimeHunt.

Service Types

UptimeHunt supports multiple monitoring service types:

Monitoring Type Comparison

Creating Services

Service Creation Workflow

1. Navigate to Services dashboard
2. Click "Add Service" button
3. Select monitoring type (HTTP or PING)
4. Configure service parameters
5. Save configuration

Common Configuration

All service types share these configuration options:

Service Name (Required) — Descriptive identifier for the service. Displayed in dashboard and reports. Maximum 128 characters.

Project (Optional) — Project assignment for organization. Select from existing projects or leave unassigned.

Enabled (Toggle) — Controls whether monitoring is active. Enabled: Service is actively monitored. Disabled: Service configured but not monitored.

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

Type-Specific Configuration

Each service type requires additional configuration:

HTTP Services

• URL endpoint
• HTTP method
• Authentication credentials
• Custom headers
• POST data

PING Services

• IP address or domain name

Refer to type-specific guides for detailed configuration instructions.

Editing Services

Edit Service Configuration

To modify an existing service:

Method 1: Quick Edit

1. Locate service in dashboard
2. Click the Edit icon (pencil)
3. Modify configuration in modal
4. Click "Save Changes"

Method 2: Detail Page Edit

1. Click service name to open details
2. Click "Edit Service" button
3. Modify configuration in modal
4. Click "Save Changes"

Editable Parameters

All service parameters can be modified:

• Service name
• Project assignment
• Enabled status
• Check interval
• Type-specific settings (URL, IP, authentication, etc.)

Deleting Services

Delete Process

To remove a service:

1. Locate service in dashboard
2. Click the Delete icon (trash)
3. Confirm deletion in dialog
4. Service is permanently removed

Deletion Consequences

Service deletion is permanent and includes:

• Service configuration removal
• Historical check data deletion
• Performance metrics removal
• Alert configurations (when implemented)

Batch Deletion

Batch deletion is not currently supported. Services must be deleted individually.

Service Status

Status Indicators

Services display current status:

Up (Operational) — Service responding successfully. Indicator: Green check mark. Last successful check displayed.

Down (Failing) — Service not responding or returning errors. Indicator: Red X mark. Error information available in details.

Pending — First check not yet completed. Indicator: Gray clock. Wait for first check interval.

Status Determination

HTTP Services

Status determined by:

• HTTP response received
• Status code 2xx or 3xx (configurable)
• Response time within timeout
• No connection errors

PING Services

Status determined by:

• ICMP echo reply received
• Packet loss below threshold
• Response time within acceptable range

Service Organization

Grouping by Project

Services are organized by project on the dashboard:

Assigned Services — Appear under their project section. Inherit project color coding. Grouped with related services.

Unassigned Services — Appear in "Unassigned" section. No project association. Can be assigned to project later.

Reordering Services

Service order within projects is currently not customizable. Services appear in creation order or alphabetically (implementation-dependent).

Service List Views

Grouping and Organization

All services are organized by project:

• Project Groups — Services grouped under their assigned project. Each group has a collapse/expand control to focus your view.
• Unassigned — Services with no project assignment appear in a separate section.
• Needs Attention — A section pinned at the top of your list surfaces any service that's currently down or degraded.

View Modes

Select your preferred view mode in Settings → Preferences → Lists layout — each option card shows a small schematic preview of the layout it produces, and the choice follows your account everywhere you sign in:

Normal View — Two-line rows, full detail. Shows the service name and target stacked, current status, per-cycle history ticks, and average latency. Balanced for scanning and detail.

Dense View — Single-line rows, max monitors per screen. Compresses rows and history strips for maximum service count per screen. Status and ticks remain visible and scannable. Best for accounts with hundreds of services or when space is limited.

Cards View — Displays services as cards in a grid layout. Each card shows the service name, target, status indicator, history ticks, and average latency. Better for visual scanning and touch-friendly interaction.

Normal and Dense views display each project group in its own quiet, bordered box on a flat page — a collapse/expand control, consistent spacing, and a column-header row (Normal) or tighter packed rows (Dense). Cards view is deliberately boxless: the group's eyebrow header sits above a bare grid of card tiles directly on the page, with no group container — each card keeps its own individual border, but the group itself isn't boxed. The needs-attention section and unassigned group remain pinned at the top, giving you quick access to services requiring action.

History Ticks

Each service displays per-cycle history ticks — small status blocks representing the recent check history. The strip packs each cycle's result as densely as the space allows, letting you see more history at a glance:

• Green — Up (the check succeeded)
• Amber — Degraded: some (but not all) probes reporting in the bucket failed transport reachability, or a result couldn't be attributed to any probe. Also used when a persisted incident marks the period degraded because an assertion failed while the target stayed reachable. A bucket only turns red when ALL probes reporting in it are down (a total outage) — a single failing probe out of many is degraded, never down.
• Red — Down (the check failed, or the target was unreachable)
• Gray hollow outline — Missed (no result arrived for a scheduled cycle — never rendered red)
• Current cycle — The rightmost tick updates live as the active check cycle progresses

Hover over a tick to see the check timestamp and result. The history strip height scales efficiently so you can fit more services on screen without sacrificing legibility.

Each bar's height now also encodes its response time, so a bucket that was merely slow visibly stands taller than a fast one at a glance, before you ever open the detail page. A missed cycle still renders as a fixed-height hollow block rather than collapsing to zero — no result means no data, not a fast result, so it must never look like the fastest bar on the strip.

Service Details View

Click a service name to navigate to its detail page, which shows:

• Complete configuration
• Check history table
• Performance metrics
• Probe location data
• Edit and management options

Bulk Operations

Currently Unavailable

The following bulk operations are not yet implemented:

• Bulk editing
• Bulk deletion
• Bulk enable/disable
• Bulk project assignment
• Batch export

Workarounds

For managing multiple services:

• Use projects for logical grouping
• Apply consistent naming conventions
• Document service purposes
• Use API for programmatic management

Service Limits

Account Limits

Service limits may apply based on account type:

Current Implementation

• No enforced limits (subject to reasonable use)
• Performance may degrade with excessive services
• Future plans may include tiered limits

Recommended Limits

For optimal performance:

• Standard accounts: Up to 100 services
• Consider performance impact of check intervals
• Balance between coverage and resource usage

Service Templates

Service templates are not currently implemented. Future versions may include:

• Predefined service configurations
• Template creation from existing services
• Template sharing capabilities
• Quick service deployment from templates

Import/Export

Current Functionality

Import and export features are not yet available.

Planned Features

Future releases may support:

• Service configuration export (JSON/YAML)
• Bulk service import
• Configuration backup
• Migration between accounts

Troubleshooting

Service Not Creating

If service creation fails:

1. Verify all required fields are completed
2. Check for validation errors in form
3. Ensure service name is unique
4. Verify URL/IP format is correct
5. Review authentication credentials

Service Not Updating

If edits don't save:

1. Check for form validation errors
2. Verify you have edit permissions
3. Refresh page and try again
4. Check browser console for errors

Services Not Displaying

If services don't appear in dashboard:

1. Verify you're logged into correct account
2. Check that services weren't deleted
3. Refresh the browser page
4. Clear browser cache
5. Try different browser

Status Not Updating

If service status seems stuck:

1. Wait for next check interval
2. Verify service is enabled
3. Check service details for recent checks
4. Ensure probers are operational
5. Review check history for patterns

Best Practices

Naming Conventions

Use clear, descriptive names:

Good Examples:
- Production API - User Authentication
- Staging Website - Homepage
- Database Server - Primary (192.168.1.10)

Poor Examples:
- Service 1
- Test
- API

Configuration Management

Maintain consistent configurations:

• Document authentication credentials securely
• Use environment-specific projects
• Set appropriate check intervals
• Enable only necessary services

Monitoring Strategy

Develop effective monitoring:

• Monitor critical paths and dependencies
• Set realistic check intervals
• Balance coverage vs. resource usage
• Use appropriate monitoring types

Organization

Maintain clean service organization:

• Assign services to projects
• Use consistent color coding
• Remove unused services
• Document service purposes

Related Documentation

• HTTP Monitoring
• PING Monitoring
• Service Details
• Projects
• Dashboard
• API Services Endpoints