Help
OpsFlow
Monitor website uptime, latency, and alerts before small outages become client problems.
OpsFlow is the operations monitoring module inside ConnectEngine OS. The active documented version focuses on basic website monitoring: a site list, status dots, site detail pages, check timelines, uptime percentages, alert history, and per-site alert configuration.
The monitoring workflow runs every 15 minutes through n8n. It checks active sites with a HEAD request and a GET fallback, stores results in OpsFlow tables, respects alert configuration and quiet hours, and sends Telegram alerts when configured thresholds are crossed.
Quick start
- Sign up for ConnectEngine OS and open OpsFlow from the dashboard.
- Add the first website you want to monitor from the OpsFlow site list.
- Confirm the site appears with a status dot and that monitoring is active.
- Set alert rules for the site, including latency threshold, consecutive failures, quiet hours, and notification toggle.
- Wait for the 15-minute uptime check workflow to record the first check.
- Open the site detail page to review the check timeline, uptime percentages, and alert history.
- Treat the first stored check plus a visible site detail timeline as the first successful run.
Core features
Site list
The OpsFlow dashboard lists monitored sites with status dots and basic management actions. The documented active UI supports adding sites, deleting sites, and pausing or resuming monitoring for a site.
Site detail
Each monitored site has a detail view with 24-hour, 7-day, and 30-day uptime percentages. The page also shows alert history and a timeline of recorded checks so recent behavior is visible without digging into logs.
Uptime check workflow
The active n8n workflow runs every 15 minutes. It checks all active sites, uses HEAD first and GET as fallback, records results, and sends alerts when rules say a notification should fire.
Latency tracking
OpsFlow stores check data in ops_checks and uses latency thresholds as part of per-site alert configuration. The marketing site mentions latency tracking and alerts, and the source docs confirm latency threshold configuration is active.
Alert rules
Alert rules are configured per site. The documented fields include latency threshold, consecutive failures, quiet hours, and a notification toggle. This lets a site alert only after the failure pattern matters to the user.
Telegram notifications
OpsFlow sends Telegram alerts when monitored sites go down or cross configured alert rules. The current documented implementation uses the ConnectEngine alerts bot and respects per-site quiet hours.
Monitoring data model
OpsFlow stores monitored sites in ops_sites, individual checks in ops_checks, and alerts in ops_alerts. The docs also mention client notification configuration and channels for per-client quiet hours and routing.
Settings explained
Common pitfalls
- The active documented module is basic monitoring. GA4 analytics and automated operational reports are roadmap or scaffold items, not current public features.
- A single slow response may not alert if consecutive-failure rules require more than one failed check.
- Quiet hours can make a real alert appear delayed because notifications are intentionally suppressed during that window.
- Paused sites remain in the dashboard, but monitoring is not active until resumed.
- The weekly digest workflow is documented as scaffold or backlog and should not be treated as live customer functionality.
What's next
Use these routes when you need help setting monitoring expectations, want early access, or want background on the automation platform.