Slack Integratie - StatusBewaker
Real-time monitoring for Dutch infrastructure
Intro
Connect Your Monitoring to Slack
Route uptime alerts from StatusBewaker directly into your team’s #ops-rotatie or #platform-status channels. Our native Slack integration pushes structured incident reports, recovery confirmations, and scheduled maintenance windows within 200 milliseconds of detection.
The connection uses encrypted HTTPS webhooks compatible with Slack’s legacy and custom app endpoints. Once linked, StatusBewaker automatically formats JSON payloads with incident severity, affected endpoints like api.groenewind.nl or cdn.rijksdienst.nl, and direct links to your public status page. No third-party bridges or Zapier accounts required.
Steps
Step-by-Step Setup Guide
1. Generate a Slack Webhook URL
Navigate to your Slack workspace settings, select Apps > Manage Apps, and install the Incoming Webhooks integration. Create a new webhook for your target channel, then copy the generated URL starting with https://hooks.slack.com/services/T00.../B00/xxxx. Restrict channel posting permissions to prevent unauthorized broadcasts.
2. Create a StatusBewaker Webhook
Log into your StatusBewaker dashboard, open the Integration panel, and click Add Webhook. Paste your Slack URL into the Endpoint field. Enable TLS verification and set the timeout threshold to 5 seconds. Save the configuration to generate a unique webhook ID for tracking.
3. Link the Endpoints
Assign the new webhook to your active monitoring groups. Select specific check types such as HTTP 200 validation, SSL certificate expiry tracking for .nl domains, or TCP port 443 availability. Click Activate to push a test payload and verify delivery in your Slack channel within 10 seconds.
Config
Alert Message Configuration
Fine-tune how StatusBewaker delivers notifications to avoid channel fatigue while ensuring critical outages reach your on-call engineers immediately. Every parameter adjusts in real-time without requiring webhook regeneration.
Configure message throttling to batch multiple endpoint failures into a single summary block, set severity thresholds to only trigger P1 and P2 incidents, or schedule quiet hours between 22:00 and 06:00 CET for non-critical routine checks. Custom fields allow you to inject runbook links, PagerDuty escalation paths, or internal Jira ticket prefixes directly into the Slack card layout.
Throttling & Frequency
Limit notifications to one alert per 15-minute window per monitoring group. Enable auto-resolution messages that fire only after 3 consecutive successful checks, preventing false-positive noise during rolling deployments or scheduled DNS propagation.
Custom Payload Fields
Map StatusBewaker variables to Slack blocks using Handlebars syntax. Insert {{incident_id}}, {{affected_service}}, {{response_time_ms}}, and {{status_page_url}} to build consistent, scannable messages that match your internal incident response playbook.