> ## Documentation Index
> Fetch the complete documentation index at: https://laraowl.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts & integrations

> Get notified the moment something breaks, on the channels your team uses.

LaraOwl watches your applications and pushes alerts to the tools your team already works in. Configure channels and triggers per project so the right people hear about the right problems — without alert fatigue.

## Notification channels

Connect one or more channels in **Project Settings → Integrations**:

| Channel      | What you get                            |
| ------------ | --------------------------------------- |
| **Slack**    | Rich block messages with action buttons |
| **Discord**  | Embedded messages with fields           |
| **Telegram** | Markdown-formatted bot messages         |
| **Email**    | Plain-text notifications                |
| **Webhooks** | JSON payload delivered to any endpoint  |

<Info>
  Email alerts and team invitations require a working mailer. Configure SMTP in your `.env` before relying on the email channel — see [Configuration](/configuration#mail-for-alerts-and-team-invitations).
</Info>

## Alert triggers

Enable the triggers you care about in **Settings → Alert Rules**:

* **New exception detected** — a previously unseen error appears.
* **High latency / slow performance** — response times degrade.
* **Uptime down** — an uptime check fails.
* **Heartbeat failure** — a cron or scheduled task stops checking in.
* **Error spike** — errors exceed a configurable threshold within a configurable window.

<Tip>
  Enable **throttle control** to collapse repeated notifications during an incident. This prevents alert fatigue when a single failure would otherwise fire hundreds of messages.
</Tip>

## Performance thresholds

Beyond reactive alerts, set proactive performance budgets per project. When a threshold is exceeded, LaraOwl **automatically creates an issue** so regressions surface before your users notice:

* Route response-time limits
* Job execution-time limits
* Query execution-time limits
* Command runtime limits

Configure these in **Settings → Thresholds**.

## Recommended setup

<Steps>
  <Step title="Connect a channel">
    In **Project Settings → Integrations**, connect Slack, Discord, Telegram, email, or a webhook.
  </Step>

  <Step title="Enable triggers">
    In **Settings → Alert Rules**, turn on the triggers relevant to the project (start with new exceptions and uptime down).
  </Step>

  <Step title="Set thresholds">
    In **Settings → Thresholds**, define response-time, query, job, and command budgets.
  </Step>

  <Step title="Tune throttling">
    Enable throttle control so incidents don't flood your channels.
  </Step>
</Steps>