Skip to main content
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:
Email alerts and team invitations require a working mailer. Configure SMTP in your .env before relying on the email channel — see Configuration.

​
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.
Enable throttle control to collapse repeated notifications during an incident. This prevents alert fatigue when a single failure would otherwise fire hundreds of messages.

​
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.
1

Connect a channel

In Project Settings → Integrations, connect Slack, Discord, Telegram, email, or a webhook.
2

Enable triggers

In Settings → Alert Rules, turn on the triggers relevant to the project (start with new exceptions and uptime down).
3

Set thresholds

In Settings → Thresholds, define response-time, query, job, and command budgets.
4

Tune throttling

Enable throttle control so incidents don’t flood your channels.