Alerts & Notifications
Slack Integration
Lighthouse sends alerts directly to Slack. Connect your workspace via OAuth, then choose a channel for each metric.
Connecting Slack
Navigate to your communication sources settings and click Connect Slack. You'll be redirected to Slack's OAuth authorization screen.
- 1Authorize the Lighthouse app — Click Allow in Slack. This grants Lighthouse permission to post messages to channels you select.
- 2Return to Lighthouse — You'll be redirected back automatically. The Slack workspace appears as a connected communication source.
- 3Select a channel per metric — When configuring a metric's notification settings, choose the connected Slack workspace and the channel where alerts should appear.
Alert message structure
Each Slack alert contains the following information:
| Field | What it shows |
|---|---|
| Metric name | The name you gave the metric in Lighthouse |
| Severity | The severity level (S0–S5) you assigned to the metric |
| Segment | Which segment combination triggered the alert, if segments are enabled |
| Current value | The metric's value in this run (e.g. 1,840 transactions) |
| Baseline | The expected value from the trend comparison (e.g. 3,240 transactions) |
| Threshold | The condition that was breached (e.g. > 30% drop) |
| Comparison | How the baseline was calculated (e.g. same day last 4 weeks) |
| Triggered at | The timestamp of the metric run that fired the alert |
Example alert using customized threshold filter variables — the default template shows metric name, description, severity, segment, and value only.
#data-alerts
Transactions volume, last 3 hrs triggered
2 min agoAlert buttons
Every alert message includes interactive buttons. Once a button is used, it's hidden on subsequent messages for the same alert instance.
| Button | What it does |
|---|---|
| 🚨 Mark as Hit | Confirms the alert is real and worth investigating. Sets a 'hit' flag on this segment run. The metric continues monitoring — this doesn't resolve or clear the alert. |
| ✅ Mark as Resolved | Marks the alert as resolved and clears the segment match state. The next metric run starts fresh — if the threshold is still breached it will fire a new alert. |
| 👍 Acknowledge | Signals that someone has seen the alert. On per-segment alerts, acknowledges at the segment level. On aggregated alerts, acknowledges at the metric-run level. |
| More Info | Opens the metric detail page in the Lighthouse app. Always present, regardless of alert state. |
Aggregated alerts
By default, each breaching segment sends its own Slack message. For metrics with many segments, this can create a lot of messages. Enable aggregated mode on the metric's notification settings to group all breaching segments from a single run into one Slack message.
In aggregated mode, the Acknowledge button operates at the metric-run level rather than per segment.
Reconnecting Slack
If your Slack integration stops working — for example, because the bot was removed from a channel or the OAuth token expired — you'll see a COMMUNICATION_SOURCE error on affected metrics. Go to communication sources settings and reconnect the workspace via OAuth to restore the integration.
Verify that the Lighthouse bot is still invited to any private channels you're using — bot access is managed in Slack directly, not in Lighthouse.