Your First Monitor

Create an HTTP monitor with custom settings, choose check regions, and understand your uptime and response time data.

Creating an HTTP monitor

From your project dashboard, navigate to Monitors > New Monitor and select HTTP as the type. You’ll see the full configuration form with several sections.

Basic settings

  • Name — A descriptive label (e.g., “Production API Health Check”).
  • URL — The endpoint to check. Must include the protocol (https://).
  • Method — GET, POST, PUT, PATCH, DELETE, or HEAD. GET is the most common for health checks.
  • Expected status code — The HTTP status code that indicates success. Defaults to 200. Set this to 201, 204, or whatever your endpoint returns.

Request configuration

For endpoints that require authentication or specific headers:

  • Headers — Add custom request headers as key-value pairs. Useful for Authorization, Accept, or API key headers.
  • Request body — For POST/PUT/PATCH methods, add a JSON body to send with each check.
  • Timeout — How long to wait for a response before marking the check as failed. Default is 30 seconds.

Check interval and regions

  • Interval — How often Signalog runs the check. Options range from 30 seconds to 15 minutes. Shorter intervals catch issues faster but use more of your plan’s check quota.
  • Regions — Select which geographic regions run the check. Available regions include US East, US West, Europe, and Asia-Pacific. Selecting multiple regions helps you detect regional outages.

Keyword monitoring

Optionally enable keyword checking to verify the response body contains (or does not contain) a specific string. This catches cases where a server returns 200 OK but serves an error page.

Confirmation count

Set how many consecutive failures are required before the monitor transitions to a Down state and triggers alerts. A confirmation count of 2 means Signalog will re-check once before alerting, reducing false positives from transient network blips.

Reading your results

After creating the monitor, the detail page shows:

  • Current state — Up, Down, or Degraded, with a timestamp of the last state change.
  • Uptime percentage — Calculated as successful checks / total checks over the selected time range (24h, 7d, 30d, or 90d).
  • Response time chart — A time-series graph of response times with P50, P95, and P99 latency lines.
  • Check history — A table of recent checks showing status code, response time, region, and timestamp.

Enabling anomaly detection

On the monitor settings page, toggle Anomaly Detection to on. Signalog will learn your endpoint’s normal response time pattern and alert you when response times deviate significantly — even if checks still pass. This helps you catch performance regressions before they become outages.

Next steps