Cron monitoring + Infrastructure observability

Your operations are silently failing.
You'll find out when a customer complains.

SyncGuard watches your scheduled jobs and network infrastructure. Missed cron runs, offline routers, weak OLT signal — one platform detects it all and tells you exactly what's affected before anyone opens a support ticket.

app.syncguard.dev/dashboard
SyncGuardSyncGuard
Dashboard
Incidents
Jobs
Infrastructure
Settings
Dashboardpayments workspace
3
Open Incidents
6/6
Devices Online
8
Active Jobs
12m
MTTR
Active IncidentsOpen · Recovering
daily-reportdaily-reportHighOpen5 tenants
invoice-exportinvoice-exportHighOpen12 tenants
data-syncdata-syncHighRecovering2 tenants
terminal

Something is always breaking. The difference is whether you find out first.

Without SyncGuard

  • Cron job silently stops running at 2am across 23 customers
  • Router goes offline — you find out from a user complaint
  • OLT signal degrades — ONUs drop one by one over hours
  • On-call wakes up with no idea what broke or who's affected

Your team spends the morning in triage. Not the fix.

With SyncGuard

  • Missed run detected within 60 seconds — incident opens
  • Router offline → Slack alert in seconds with device name
  • Weak ONU signal rule fires before customers notice
  • One clear signal: what failed, when, and who's impacted

Fix deployed in 40 minutes. Most customers never noticed.

One platform for jobs and infrastructure. Stop building monitoring hacks.

Cron job reliability, SNMP device monitoring, and infrastructure alerting — unified in one system your team actually uses.

Cron job monitoring, per tenant

SyncGuard polls every registered job every minute. The moment a run is overdue it starts counting missed runs per tenant — so you know exactly which customers are affected.

SNMP device monitoring

Poll routers, OLTs, switches, and UPS units via SNMP. Track CPU, memory, optical signal quality, interface traffic, and PON ONU status — all in one place.

One incident, not a storm of alerts

Events roll up into a single incident that stays open until recovery. Rule-based triggers with configurable thresholds, duration, and cooldown. Incidents reopen automatically if the issue returns.

Alerts where your team already works

Slack, PagerDuty, OpsGenie, and Teams — configured per workspace. Device incidents show the device name and rule. Job incidents show affected tenants and missed runs.

Infrastructure map

Visualise all your devices on an interactive map. Color-coded by status — spot offline devices at a glance. Works with OpenStreetMap, no API key required.

OLT optical signal quality

Per-PON Rx power in dBm for every ONU. Alert when signal degrades below threshold. See which specific ONUs are weak and exactly how weak they are.

How it works

Two monitoring modes. One platform.

01

Register a job and set its schedule

Create a monitored job in the dashboard. Set the expected interval, grace period, and the thresholds that should trigger an incident.

POST /jobs {"jobKey":"daily-report", "expectedIntervalSeconds":86400, "gracePeriodSeconds":300}
02

Ping SyncGuard after each run

Add one HTTP call at the end of your cron script. SyncGuard tracks last-seen per tenant and counts missed runs when the window expires.

POST /jobs/daily-report/ping {"tenantId":"customer-8821", "status":"success"}
03

Get alerted. Track recovery. Close the loop.

When runs are missed, your team gets one clear alert showing which customers are affected. SyncGuard closes the incident automatically when pings resume.

alerts → Slack, PagerDuty, Teams affectedTenants: [customer-8821] missedRuns: 2
< 60sTime from missed run or offline device to open incident
SNMPNative device polling — routers, OLTs, UPS, switches
4 channelsSlack, PagerDuty, OpsGenie, Teams
Per tenantMissed runs tracked per customer

Pay for what you monitor. Nothing else.

No per-seat fees. No ping volume caps. No surprise overages. Pricing that scales with how many jobs you actually watch.

What is a monitored job? One registered cron job in your workspace. If you have a daily-report job and an invoice-export job, that's 2 monitored jobs. Tenant count and ping volume are unlimited — you pay based on how many distinct jobs you monitor.

Free

Free

forever · no credit card

  • 5 monitored jobs
  • 2 tenants
  • 100 pings / day
  • 7-day incident history
  • Email alerts only
Get started free
Most popular

Starter

$19/mo

per month

  • 15 monitored jobs
  • Unlimited tenants
  • Unlimited pings
  • Slack, PagerDuty, Teams
  • 90-day incident history
Get started

Growth

$49/mo

per month

  • 50 monitored jobs
  • Unlimited tenants
  • Unlimited pings
  • Slack, PagerDuty, Teams
  • 180-day incident history
  • Priority email support
Get started

Your operations are running. But is everything working?

Silent failures — missed cron runs, offline devices, degraded signal — erode trust before anyone files a ticket. Start monitoring for free.