Monitoring

Monitoring is pull-based probing from Mydle workers against targets you configure. Quiet charts mean no checks have run yet, not a fake green score.

• Rules — one monitor per target and kind (HTTP, SSL, or DNS).
• Checks — scheduled executions with pass/fail and timing from the probe.
• Health — project health contributors built only from observed results.
• Alerts — opened (and optionally notified) when evaluation rules match failures.

• HTTP — availability and response expectations (Free and above).
• SSL — daily certificate validity and expiry checks for each active HTTP monitor’s hostname.
• DNS — daily DNS resolution checks for each active HTTP monitor’s hostname.

Setup catalog entries marked Coming soon (store listings, Firebase, privacy, app-ads) cannot be activated — they do not score health.

Continuous scheduling requires production Trigger workers. Without them, monitors exist as configuration but do not run on a cadence. Local or manual probe paths may exist for development; treat empty check history as honest, not estimated.

Check results feed project health, alerts, incidents, and status page components when those features are entitled and wired.

• Free — 3 HTTP monitors every 10 minutes.
• Pro — 10 HTTP monitors every 5 minutes, alert integrations, incidents and status pages. Both plans include daily SSL and DNS checks and outage emails. See Limits & Quotas.

Continuous execution still needs Trigger credentials in production on every plan that schedules checks.

• HTTP Monitoring
• SSL Monitoring
• DNS Monitoring
• Health & Checks
• Alerts
• In the product: /app → project → Monitoring · API: OpenAPI (Enterprise API keys).