Skip to main content

Monitor Settings

Monitor settings control how Ninja Uptime checks your endpoints and determines whether they are healthy.

You can configure these settings when creating or editing a monitor.

Configuration Options​

Account​

The account that owns this monitor.

This determines:

  • Access permissions
  • Alert routing
  • Organization of monitors

URL​

The full URL of the endpoint you want to monitor.

Examples:

  • https://example.com
  • https://api.example.com/health

Make sure the URL is publicly accessible and returns a valid response.

Check Interval​

How often the monitor is checked.

Example:

  • 30s = check every 30 seconds

Shorter intervals:

  • Detect issues faster
  • Increase monitoring frequency

Longer intervals:

  • Reduce system load
  • May delay detection

Timeout​

The maximum time to wait for a response before considering the check failed.

Example:

  • 10s = fail if no response within 10 seconds

Set this based on your application’s expected response time.

Expected HTTP Status​

The HTTP status code considered a successful response.

Examples:

  • 200 OK — Standard success response
  • 301 Moved Permanently — Valid for redirects
  • 302 Found — Temporary redirect

If the response does not match this value, the monitor may be marked as failed.

How Settings Affect Monitoring​

These settings directly impact how issues are detected:

  • Interval + Timeout determine responsiveness
  • Expected Status defines what “success” means
  • SSL Monitoring adds additional validation checks

Incorrect configuration may result in:

  • False positives (reporting issues when none exist)
  • Missed downtime

Common Configurations​

Standard Website​

  • URL: https://example.com
  • Interval: 30s – 1m
  • Timeout: 5s – 10s
  • Expected Status: 200 OK

Redirected Domain​

  • URL: http://example.com
  • Expected Status: 301 Moved Permanently

API Endpoint​

  • URL: https://api.example.com/health
  • Expected Status: 200 OK
  • Timeout: Lower (e.g., 3s – 5s)

Best Practices​

  • Use HTTPS whenever possible
  • Set realistic timeouts based on your app performance
  • Match expected status codes to actual behavior
  • Enable SSL monitoring for production systems
  • Avoid overly aggressive intervals unless necessary

Updating a Monitor​

After making changes:

  1. Click Update Monitor
  2. Changes take effect immediately