Monitoring & Alerts

jokowipe.id provides real-time monitoring of all your backup jobs and agents, with configurable alerts delivered to your preferred channels.

Real-Time Status Page

Go to Monitoring to see a live dashboard of:

• All active backup jobs (running now)
• Agent heartbeat status
• Failed backup jobs (last 24h)
• Schedule compliance (did all scheduled backups run on time?)

Alert Rules

Alert rules define the conditions that trigger notifications.

Built-in Alert Types

Alert Type	Trigger Condition
Backup Failed	A backup job returns a non-zero exit code
Backup Missed	A scheduled backup window passed without a successful run
Agent Offline	An agent stops sending heartbeats for >5 minutes
Storage Almost Full	Free space in a storage target drops below threshold
Backup Size Anomaly	AI detects an unusual size change (see Anomaly Detection)
Duration Anomaly	Backup takes significantly longer or shorter than usual
Backup Expired Warning	Backups are expiring faster than new ones are created

Creating Custom Alert Rules

1. Go to Monitoring → Alert Rules → New Rule
2. Select Trigger Condition
3. Configure thresholds (e.g., "alert if backup fails 2 times in a row")
4. Select Notification Channels
5. Set Severity (info, warning, critical)
6. Click Save

# Example rule via API
rule:
  name: "postgres-prod-failure"
  type: backup_failed
  conditions:
    consecutive_failures: 2
    agent_ids:
      - agent-a1b2c3
  severity: critical
  channels:
    - slack-prod-alerts
    - pagerduty-oncall

Notification Channels

Email

All users receive backup failure alerts at their account email by default. You can configure additional email recipients per organization.

Slack

1. Go to Monitoring → Channels → Add Slack
2. Authorize the jokowipe Slack app
3. Select your Slack channel
4. Configure which alert types to send to this channel

See Slack Integration → for details.

Telegram

Send alerts to a Telegram bot or group chat. See Telegram Integration →.

PagerDuty

Integrate with PagerDuty for on-call escalation. See PagerDuty Integration →.

Custom Webhooks

Send HTTP POST notifications to any endpoint. See Custom Webhooks →.

Alert Severity Levels

Level	Color	Typical Use
Info	Blue	FYI events (backup completed, schedule modified)
Warning	Yellow	Issues that need attention but are not critical
Critical	Red	Immediate action required (backup failed, agent down)

Silencing Alerts

Temporarily silence an alert rule (e.g., during planned maintenance):

1. Go to Monitoring → Alert Rules
2. Click the rule → Silence for...
3. Choose duration: 1 hour, 4 hours, 24 hours, or custom
4. Optionally add a note (shown in the silence history)

Alert History

Go to Monitoring → Alert History to see all past alerts, including:

• Triggered at
• Alert type and severity
• Which channels were notified
• Whether the alert was acknowledged

Backup SLA Tracking

Configure an SLA window for each schedule. jokowipe.id will alert if a backup doesn't complete within the SLA:

schedule:
  name: "postgres-prod-daily"
  cron: "0 2 * * *"
  sla:
    max_duration_minutes: 60    # Alert if backup takes >60 min
    must_complete_by: "04:00"   # Alert if not done by 4 AM (same timezone)