Microsoft Teams Integratie - StatusBewaker
Real-time monitoring voor Nederlandse infrastructuur
Introduction
Route critical uptime alerts directly into your operational channels. StatusBewaker delivers structured downtime notifications using Microsoft Adaptive Cards, ensuring your SRE and NOC teams receive actionable context without leaving Teams.
When a monitored endpoint like api.ziggo.nl or your internal erp.stratusdata.eu drops below a 200ms response threshold, the integration pushes a formatted card containing incident severity, affected region (e.g., NL-AMS01), recovery ETA, and direct links to the status dashboard. This eliminates platform context switching and keeps incident response aligned with your existing Microsoft 365 workflows.
Setup Steps
Generate a Teams Incoming Webhook
Navigate to your target channel (e.g., #ops-netherlands), select Connectors, and add the Incoming Webhook app. Copy the generated URL ending in /teamswebhook/... Store this securely in your StatusBewaker environment variables as TEAMS_WEBHOOK_URL.
Configure Adaptive Card Payload
StatusBewaker uses v1.5 Adaptive Card schemas. Enable the teams_adaptive toggle in your integration settings. The system will automatically map your endpoint groups to card sections, injecting live metrics like last_heartbeat: 14:02:11 CET and packet_loss: 2.4%.
Validate & Trigger Test
Run a dry-run simulation from the dashboard. You should receive a card titled ⚠️ StatusBewaker Alert: NL-ROT02 Gateway Degraded within 12 seconds. Verify that the Resolve Incident button correctly routes to your PagerDuty or ServiceNow ticketing queue.
Configuration
Fine-tune alert routing and card rendering to match your team’s incident response playbook.
By default, StatusBewaker batches notifications to prevent Teams channel fatigue. Set ALERT_COOLDOWN=300 to suppress duplicate pings during prolonged outages. You can also define custom JSON overrides for card styling, such as changing the severity accent color from attention to error for critical ERP failures. Webhook authentication is handled via Azure AD app-only tokens; ensure your service principal has ChannelMessage.Send permissions in the target Teams group. For multi-region deployments, append ?region=nl to your webhook endpoint to route Amsterdam-specific alerts to #infra-west while keeping Rotterdam traffic in #infra-east.
Open Integration Console View Payload Reference