Endpoint Monitoring

Endpoint Monitoring tracks configured HTTP and HTTPS URLs for availability, uptime, response time, and alert state so operations teams can identify down or slow services before customers report an outage.

Endpoint And Uptime Naming

Bitaic uses Endpoint Monitoring as the product name in docs, navigation, search, API examples, and CLI examples. Uptime Monitoring remains a user-facing alias for availability-focused workflows and maps to this same product page.

When To Use It

• Use Endpoint Monitoring when a specific URL, application endpoint, or web service must remain available and responsive.
• Use Certificate Monitoring when the risk is SSL/TLS certificate status or certificate expiration for an HTTPS endpoint.
• Use DNS Monitoring and Domain Monitoring when the risk is resolution, nameserver behavior, registrar state, or domain expiration.
• Health Monitoring is private beta only until its Q1 2027 public release.

Prerequisites

• A Bitaic account with permission to configure monitored targets and alert thresholds.
• One or more HTTP or HTTPS endpoint URLs that product, operations, or support teams consider critical.
• Expected availability behavior for each URL, including whether a slow response should become an alert.
• Notification routing for downtime, slow response time, and optional SSL expiration alerts.

What Bitaic Checks

• Endpoint URL and latest availability state.
• HTTP method, final status code, redirect count, and final URL.
• Uptime and downtime history for the monitored target.
• Response time for each endpoint check in whole milliseconds.
• Slow or unavailable service conditions.
• Certificate Monitoring status when certificate checks are enabled for the same HTTPS target.
• Response-time warning and critical thresholds for the endpoint.

Check Behavior

Response-Time Thresholds

Configuration Example

endpoint-agent-config.yml
endpoints:
  - url: https://your-domain.com
    method: GET
    follow_redirects: true
    max_redirects: 5
    expected_status_codes:
      - 200-399
    check_interval_seconds: 60
    timeout_ms: 10000
    thresholds:
      response_time_ms:
        warning: 1000
        critical: 3000
    ssl_alert_days: 30

Setup Flow

1. Add the endpoint URL to the monitored endpoint list.
2. Confirm the request method, redirect handling, expected status codes, check interval, and timeout for the URL.
3. Configure response-time warning and critical thresholds in the dashboard, API, or endpoint configuration surface.
4. Enable Certificate Monitoring for HTTPS endpoints when the same URL should also be watched for certificate expiration.
5. Start or refresh the endpoint monitoring collection path.
6. Confirm that the dashboard shows availability state, response time, uptime or downtime history, and alert state for the URL.

Example Workflow: Monitor a Customer-Facing Endpoint

Goal: add a critical URL to Endpoint Monitoring, verify the first availability check, and make response-time alerts operationally useful.

1. Choose the URL that best represents the service experience customers depend on, such as a health check, API route, or web page.
2. Add the URL to the endpoint configuration and set response-time warning and critical thresholds, plus optional Certificate Monitoring expiration thresholds for the target.
3. Start or refresh the endpoint monitoring collection path so Bitaic can check the URL.
4. Run a manual endpoint check or wait for scheduled collection, then confirm availability, status code, redirect count, response time, uptime state, and alert state.
5. Route downtime and slow-response alerts to the team that owns the application or service.
6. During normal operations, compare response-time history with deployments, incidents, and dependency changes when latency begins to rise.

Data, States, Alerts, And Dashboard Output

Bitaic alerts when an endpoint is unavailable, when response time crosses the configured slow-response threshold, or when Certificate Monitoring reports expiration risk for the same HTTPS target.

CLI And API

CLI support includes endpoint install, start, status, and check commands. API support includes retrieving endpoint metrics, managing monitored endpoints, and configuring response-time thresholds.

• Create or list monitored endpoints with /v1/workspaces/{workspace_id}/targets and type: "endpoint".
• Attach availability checks with /v1/workspaces/{workspace_id}/targets/{target_id}/checks and type: "endpoint_availability".
• Retrieve response-time data with /v1/workspaces/{workspace_id}/metrics and metric=endpoint.response_time_ms.
• Update response-time thresholds with /v1/workspaces/{workspace_id}/checks/{check_id} and thresholds.response_time_ms.

bitaic install agent endpoint
bitaic agent start endpoint
bitaic agent status endpoint
bitaic endpoint check <url>

$ bitaic endpoint check https://your-domain.com
url: https://your-domain.com
final_url: https://your-domain.com
method: GET
check_state: active
status_code: 200
availability: up
response_time_ms: 248
response_time_warning_ms: 1000
response_time_critical_ms: 3000
redirect_count: 0
uptime_state: available
alert_state: clear
checked_at: 2026-08-18T14:30:00Z

Troubleshooting