Ops Monitor

The Ops Monitor (System page) provides real-time visibility into the health of your GridWork HQ deployment.

Pipeline Server Status

• Connection status — whether the dashboard can reach the pipeline server
• Uptime — how long the pipeline server has been running
• Active jobs — currently executing pipeline runs
• Queue depth — jobs waiting for an available slot

The dashboard pings the pipeline server's /health endpoint to determine connectivity.

System Metrics

If Glances is running on the pipeline server machine (default port 8760), the Ops Monitor displays:

• CPU usage
• RAM usage
• Disk usage

Integration Health

Shows the configuration status of each integration:

• Notion API — configured/not configured
• GitHub API — configured/not configured
• Stripe — configured/not configured
• Vercel — configured/not configured
• Anthropic — configured/not configured

Site Health

If PAGESPEED_API_KEY is configured, displays PageSpeed Insights scores for tracked sites. If UPTIMEROBOT_API_KEY is set, shows uptime monitoring data.

Troubleshooting from the Ops Monitor

If the pipeline server shows as unreachable:

1. Verify it is running: curl http://localhost:8750/health
2. Check that PIPELINE_SERVER_TOKEN matches in both environments
3. If using Tailscale, verify the funnel is active: tailscale funnel status