Endpoint Monitoring

Endpoint Monitoring tracks configured 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 docs use Endpoint Monitoring as the canonical product name. Uptime Monitoring is a user-facing alias for availability-focused endpoint workflows.

When To Use It

  • Use Endpoint Monitoring when a specific URL, application endpoint, or web service must remain available and responsive.
  • Use SSL Monitoring when the risk is 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.
  • Use Health Monitoring when teams need host-level CPU, memory, disk, or server-resource visibility.

Prerequisites

  • A Bitaic account with permission to configure monitored targets and alert thresholds.
  • One or more 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.
Permission requirement

Use a Bitaic role that can manage monitored targets, alert policies, and notification routing before adding or changing Endpoint Monitoring checks.

What Bitaic Checks

  • Endpoint URL and latest availability state.
  • Uptime and downtime history for the monitored target.
  • Response time for each endpoint check.
  • Slow or unavailable service conditions.
  • SSL certificate status when SSL checks are enabled for an HTTPS endpoint.
  • Dashboard alert-threshold state for the endpoint.

Configuration Example

Configuration note

Endpoint Monitoring uses an endpoint agent configuration with a list of monitored URLs. Configure downtime, slow-response, and optional SSL expiration thresholds from the dashboard or configuration surface.

endpoint-agent-config.yml
endpoints:
  - url: https://your-domain.com
    ssl_alert_days: 30

Setup Flow

  1. Add the endpoint URL to the monitored endpoint list.
  2. Configure downtime and slow-response alert thresholds in the dashboard or endpoint configuration surface.
  3. Enable SSL certificate checks for HTTPS endpoints when the same URL should also be watched for certificate expiration.
  4. Start or refresh the endpoint monitoring collection path.
  5. Confirm that the dashboard shows availability state, response time, uptime or downtime history, and alert state for the URL.

Data, States, Alerts, And Dashboard Output

OutputPurpose
Endpoint URLIdentifies the monitored web service or application target.
Availability stateShows whether the latest check considers the endpoint available, unavailable, degraded, paused, or unknown.
Response timeRecords how long the endpoint took to respond so teams can detect latency regressions and slow-service alerts.
Uptime and downtime historyProvides the historical context needed to review reliability, incident windows, and recurring availability problems.
SSL certificate statusAppears for HTTPS endpoints when SSL Monitoring is enabled on the same target.
Alert threshold stateShows whether downtime, slow response time, or optional SSL expiration rules are clear, warning, or firing.

Bitaic alerts when an endpoint is unavailable, when response time crosses the configured slow-response threshold, or when SSL expiration is inside the configured window for endpoints with SSL checks enabled.

CLI And API

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

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
availability: up
response_time_ms: 248
uptime_state: available
alert_state: clear
checked_at: 2026-08-18T14:30:00Z

Troubleshooting

SymptomLikely causeNext check
Endpoint is unavailableThe service may be down, blocked from the collector, or returning an unexpected failure response.Check the endpoint from the same network path, then review recent uptime history and collection status.
Response time alert firesThe endpoint exceeded its configured slow-response threshold.Compare recent response-time history with application, hosting, and dependency telemetry.
Endpoint is missing from the dashboardThe URL may not be saved in the monitored endpoint list or the collection path has not picked up the latest configuration.Review endpoint-agent-config.yml, restart or refresh collection, and confirm the dashboard target list updates.
Alert does not reach the expected channelAlert routing or integration configuration may be incomplete.Review the alert policy, notification integration, and threshold state for the endpoint.
SSL alert appears on an endpointSSL checks may be enabled for the HTTPS target and the certificate is inside the configured renewal window.Review the SSL Monitoring page and confirm the configured ssl_alert_days value.