Alerts where your team already looks
Most teams notice a Slack message faster than an email, and on-call definitely does. The Slack integration connects through an OAuth bot token and posts LynxTrac events to the channels you choose.
The routing is the useful part. Severity, device group, and event type each route independently, so the #ops channel sees disk alerts while #security gets the XDR findings, and neither sees the other.
Routed, not broadcast
Routing is configured per rule and per channel, scoped by device and customer. An MSP can give each customer team its own channel without cross-talk.
Digest modes against channel fatigue
Real-time for pages, hourly or daily digests for the rest. Frequency is set per rule, so the noisy stuff batches and the urgent stuff does not.
Events worth waking up for
Health threshold breaches, heartbeat failures, patch job outcomes, deployment approvals, software policy violations, and payment failures all carry their context into the message.
Setting it up
Connect from the LynxTrac notification settings: authorize the Slack workspace, pick the channels, and map alert rules to them. The bot posts only to channels you grant.
Existing alert rules keep working; Slack is an additional channel beside email, webhook, and in-app, not a replacement.
Asked about this integration
Does the Slack bot read channel messages?
Can different customers route to different channels?
See it connected to your own account
The free tier covers 2 servers forever, which is enough to wire this up and judge it on your infrastructure rather than ours.