Jenkins Node Offline Notifications
Jenkins agent monitoring with intelligent alerting, so you never miss a node outage. Alerts go to Slack, PagerDuty, SMS, or Email once your grace period confirms a node is down.
$49/month after 30-day trial
Monitored
47
Offline
2
Alerts
5
Recent Activity
Everything You Need to Monitor Jenkins Agents
Comprehensive monitoring with intelligent alerting reduces noise while ensuring you never miss critical outages.
Multi-Channel Alerts
Send notifications to Slack, PagerDuty, Twilio SMS, and Email simultaneously. Route alerts to the right team at the right time.
Real-Time Detection
Event-driven monitoring catches node state changes instantly. Periodic reconciliation ensures nothing slips through the cracks.
Intelligent Filtering
Grace periods prevent alert noise from brief disconnections. Flapping detection suppresses alerts for unstable nodes.
Flexible Routing
Route alerts based on node names, labels, or severity levels. Priority-based policy evaluation gives you complete control.
Audit & Compliance
Complete audit trail of all alerts, suppressions, and license events. Export logs for compliance and troubleshooting.
Secure by Design
Credentials stored securely via Jenkins credential system. No sensitive data in plaintext configuration.
Four Notification Channels
Send node offline alerts wherever your team works. Use one channel or all four at once.
Slack
- Rich message formatting with node details
- Channel override per destination
- Custom message templates
- Thread-per-node option for organized alerts
- Webhook-based integration (no bot required)
PagerDuty
- Events API v2 integration
- Automatic incident resolution on recovery
- Deduplication keys scoped to each incident, preventing a collision on rapid delete-and-recreate
- Severity mapping (critical, error, warning)
- Custom routing keys per destination
Twilio SMS
- Direct SMS alerts to multiple recipients
- Rate limiting (configurable max SMS/hour)
- E.164 phone number format validation
- Custom message templates
- Per-destination configuration
- HTML and plaintext support
- Custom subject and body templates
- Uses Jenkins mailer or custom SMTP
- Multiple recipients per destination
- Configurable sender address
Looking for a notification channel not listed here? Contact us
How the Alerting Works
Detection is immediate; alerts go out once the grace period confirms the node is still down. The Worker Sentinel docs cover every setting.
Event-Driven Detection
- Jenkins ComputerListener events detect node state changes as they happen
- Tracks ONLINE, OFFLINE, and TEMPORARILY_OFFLINE states
- Periodic reconciliation scans (every 5 minutes) as backup
Grace Periods
- Configurable delay before alerting (0-3600 seconds, default 60)
- Per-destination overrides supported
- Alerts cancelled if the node recovers during the grace period
- Recovery notices follow only the destinations the outage actually alerted
Flapping Detection
- Configurable threshold (default: 5 state changes)
- Configurable window (default: 300 seconds)
- Suppresses alerts for flapping nodes, with separate flapping notifications
Deduplication
- Duplicate alerts suppressed within a window (default: 300 seconds)
- Per-destination customizable windows
Routing Policies
- Route by node name patterns (glob or regex) or Jenkins labels
- Route by alert severity (OFFLINE, RECOVERY, FLAPPING)
- Priority-based policy evaluation with stop-on-match option
Audit Logging
- In-memory buffer of 1000 recent events plus file-based daily audit logs
- Filter events by type, node and time range
- Tracks alerts sent, suppressed, and failed
Ready to Stop Missing Node Outages?
First-time subscribers get a 30-day free trial: cancel before it ends and you won't be charged.
Start Free Trial