Microsoft Teams¶
Vesana sends alerts as an adaptive card to a Microsoft Teams webhook URL.
Setup¶
1. Create a webhook in Teams¶
In the Teams channel, use Workflows to create the template "Post to a channel when a webhook request is received" and copy the generated URL. An older "Incoming Webhook" connector works as well, as long as Microsoft still accepts it.
2. Store it in Vesana¶
Alerting → Channels → New Channel → type Microsoft Teams:
| Field | Value |
|---|---|
| Name | e.g. "Teams #monitoring" (required) |
| Tenant | only selectable when creating |
| Webhook URL | from step 1 (required, must start with https://) |
| Title Prefix | optional, e.g. [Production] — put in front of every title |
Then Send test on the channel row. Which statuses and whether recoveries go through the channel is set by the alert rule.
Format¶
Adaptive card (version 1.4) with:
- title with status emoji, e.g. "🔴 Alert: Disk /var on web01.acme.local is CRITICAL"
- below it the check message (for a combined card: one line per check with its status)
- facts: Host (with IP), Check, Status, since when, Duration, Tenant — labels in the notification language
- the list of suppressed dependent devices, if any
- an Open in Vesana button
The Teams notification and activity feed show the headline and the message.
Acknowledging straight from Teams is not available; Open in Vesana leads to the device, where you acknowledge.
Delivery¶
If Teams answers with an error (e.g. 429 on rate limiting), Vesana retries the delivery with growing intervals (10 s up to 10 min, up to 8 attempts in total). With many simultaneous alerts, grouping in the alert rule helps.
Multiple tenants¶
For MSP setups create one channel per customer tenant — alert rules may only use channels of their own tenant.
Next¶
- Notification channels
- Slack — similar setup