LuminaLog
Waitlist
Features

Uptime Monitoring

Keep your services online with automated health checks and instant downtime alerts.

Availability

Uptime monitoring is available on all plans. Even on the Indie plan, you can monitor your first critical endpoint for free.

What is Uptime Monitoring?

Uptime monitoring continuously checks your web services, APIs, and endpoints to ensure they're accessible and responding correctly. When a monitor detects an issue, you'll receive instant notifications through your configured alert channels.

Each monitor performs HTTP requests at your specified interval and validates the response against your expected status code. If the endpoint fails to respond or returns an unexpected status, an alert is triggered.

Key Features

Flexible Intervals

Check your endpoints every 1, 5, or 10 minutes based on your needs and plan limits.

Multiple HTTP Methods

Support for GET, POST, and HEAD requests to monitor different types of endpoints.

Response Time Tracking

Monitor response times and identify performance degradation before it becomes critical.

Instant Alerts

Get notified immediately when your service goes down or recovers via email, Slack, Discord, or PagerDuty.

Creating a Monitor

To create an uptime monitor:

1

Navigate to the Uptime section in your dashboard

2

Click "Add Monitor"

3

Select the project this monitor belongs to

4

Enter a descriptive name for your monitor

5

Provide the URL to monitor (must be a valid HTTP/HTTPS URL)

6

Choose the HTTP method (GET, POST, or HEAD)

7

Set the check interval (1, 5, or 10 minutes)

8

Configure the timeout (1-30 seconds)

9

Specify the expected HTTP status code (e.g., 200, 204, 301)

Monitor Configuration

Check Intervals

  • 1 min - Critical services
  • 5 min - Standard
  • 10 min - Less critical

Timeout Settings

Set between 1-30 seconds. If your endpoint doesn't respond within this time, the check is considered failed.

Status Codes

  • 200 - OK
  • 204 - No Content
  • 301 - Redirects

Setting Up Alerts

To receive notifications when your monitors detect issues, you need to create an alert rule with the error type set to "uptime_monitor".

Important Configuration

Alert rules are project-specific. You must create an alert rule in each project that has uptime monitors you want to be notified about.

Creating an Alert Rule

  1. Go to your project settings
  2. Navigate to the "Alert Rules" section
  3. Click "Create Alert Rule"
  4. Enter "uptime_monitor" in the Error Type Filter field
  5. Choose your notification channels (email, Slack, Discord, PagerDuty)
  6. Configure channel-specific settings (webhook URLs, email addresses)
  7. Save the rule

Alert Behavior

When a monitor detects an issue:

Down Alert

Sent when a monitor fails for the first time.

Recovery Alert

Sent when a monitor recovers.

  • Alerts include monitor name, URL, status, error details, and timestamp
  • Direct links to the monitor details page for quick investigation

Multiple Projects

If you have monitors across multiple projects, you need to create a separate alert rule in each project. Each rule can have different notification channels and settings based on the project's requirements.

Viewing Monitor Results

Each monitor maintains a history of check results, including:

Timestamp of each check
HTTP status code received
Response time in milliseconds
Success/failure status
Error messages for failed checks

Results are retained for 7 days and displayed in charts showing uptime percentage and response time trends over the last 24 hours.

Plan Limits

Indie

1 uptime monitor with 10-minute minimum check intervals.

Bootstrapper

Up to 3 uptime monitors with 5-minute minimum check intervals.

Compliance

Up to 5 uptime monitors with 1-minute minimum check intervals.

Scale

Up to 10 uptime monitors with 1-minute minimum check intervals.

Best Practices

Use descriptive names that clearly identify checks

Set realistic timeouts based on typical response time

Monitor critical endpoints with shorter intervals

Use HEAD requests for availability-only checks

Create dedicated health check endpoints

Set up alert rules in all projects with monitors

Review response time trends periodically

Test your monitors after initial configuration

Common Use Cases

API Health Checks

Monitor your API's health endpoint. Use 1-minute interval for critical APIs.

Website Availability

Check your homepage or a specific page. 5-minute interval is typically sufficient.

Microservices

Monitor each microservice to identify which one is causing issues.

Dependencies

Monitor external services your application depends on.

Next Steps

Need Help?