SSL Monitoring

SSL Monitoring tracks SSL/TLS certificate status and expiration for configured HTTPS endpoints so operations teams can renew certificates before browser warnings, failed checks, or service outages affect users.

When To Use It

  • Use SSL Monitoring for HTTPS endpoints where certificate expiration or certificate status changes could interrupt access.
  • Use Endpoint Monitoring to track whether the same URL is available, responsive, and meeting uptime expectations.
  • Use DNS Monitoring and Domain Monitoring when the risk is record resolution, nameserver behavior, or domain status rather than the certificate itself.

Prerequisites

  • A Bitaic account with permission to configure monitored targets.
  • One or more HTTPS endpoint URLs to monitor.
  • Endpoint monitoring collection configured for the URL when SSL checks are managed through the Endpoint Monitoring workflow.
  • An explicit certificate alert threshold, such as ssl_alert_days, for the renewal notification window.
Permission requirement

Use a Bitaic role that can configure monitored endpoint targets and update certificate alert thresholds before changing SSL Monitoring settings.

What Bitaic Checks

  • Endpoint URL for the monitored HTTPS target.
  • Current SSL/TLS certificate status.
  • Certificate expiration date or days remaining.
  • Configured alert threshold in days.
  • Monitoring state and recent certificate check results.

Configuration Example

Configuration note

SSL Monitoring shares endpoint configuration with Endpoint Monitoring when the same URL is monitored for availability and certificate status. Set ssl_alert_days to control the renewal notification window for each HTTPS endpoint.

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

Setup Flow

  1. Add the HTTPS endpoint URL to the monitored endpoint list.
  2. Set ssl_alert_days to the number of days before expiration when Bitaic alerts.
  3. Start or refresh the endpoint monitoring collection path so the certificate check is picked up.
  4. Confirm that the endpoint appears in the certificate dashboard with a certificate status, expiration date, days remaining, and alert state.

Data, Alerts, And Dashboard Output

OutputPurpose
Endpoint URLIdentifies the HTTPS target whose certificate is monitored.
Certificate statusShows whether the latest certificate check is healthy or needs attention.
Expiration date or days remainingGives teams the renewal window before the certificate expires.
Alert thresholdRecords when Bitaic should notify teams before expiration.
Recent check resultHelps confirm whether the latest collection run saw the expected certificate.

Bitaic alerts when a certificate is approaching expiration based on the configured threshold. Alert routing uses the same notification and incident integrations as the rest of the Bitaic monitoring platform.

Renewal Workflow

  1. Use the dashboard alert to identify the endpoint, expiration date, and remaining renewal window.
  2. Renew or replace the certificate through the owning certificate or hosting provider.
  3. Re-run or wait for the next SSL Monitoring check after the renewed certificate is deployed.
  4. Confirm that Bitaic shows the updated expiration date and clears the expiration alert state.

CLI And API

CLI support covers installing, starting, and checking the endpoint monitoring collection path used by SSL Monitoring. API support covers retrieving certificate status and managing certificate alert thresholds.

Troubleshooting

SymptomLikely causeNext check
Certificate expiration alert firesThe certificate is inside the configured renewal window.Confirm ownership, renew the certificate, then verify the dashboard expiration date updates.
Browser warning appears after renewalThe endpoint may still be serving the old certificate or a mismatched certificate chain.Confirm the deployed certificate on the endpoint and wait for or trigger a fresh monitoring check.
Endpoint is missing from SSL MonitoringThe URL may not be configured as an HTTPS monitored endpoint.Check the endpoint configuration and confirm the collection path is running.
Alert does not reach the expected channelAlert routing or integration configuration may be incomplete.Review the alert policy and notification integration setup.