Alerts Overview
Introduction
The Alerts dashboard helps you monitor and configure automatic notifications that are sent when log data matches conditions you define. Use it to create, review, and manage alert rules that trigger webhooks or other integrations.
What are Alerts?
Alerts are user-defined rules that watch incoming log or event data and send a notification (usually via a webhook) when conditions are met. Each alert contains:
- a descriptive
Alert Nameto identify it - one or more project scopes (
Select Project) to limit where the rule applies - a set of
Filtersthat describe the trigger conditions - a
Webhookdestination and optional template variables - a
Deduplication Periodto avoid repeated notifications
Key Features
- Create Alerts: Use the
Create Newbutton to define a new alert in a guided stepper form - Edit Alerts:
Click on the Editicon to update an existing alert - Delete Alerts:
Click on the Deleteicon and confirm to remove an alert - Filter Builder: Build complex conditions with field/operator/value rules
- Webhook Template Variables: Map alert data into webhook templates
- Pagination: Browse alerts across pages using the pagination control
Dashboard Layout
Main Components
Titleand brief description at the top of the pageCreate Newprimary button to open the alert creation modal- Alerts list: card-style rows showing each alert's
Alert Nameand action icons - Pagination control at the bottom-right of the list
EditandDeleteaction icons on each alert- Modal dialog (
Create Alert/Edit Alert) with a two-step form
Navigation
- Navigate to the Alerts dashboard via the main sidebar under Alerts (or via the project settings where available).
- Use the
Create Newbutton in the top-right to begin creating an alert. - Use the pagination control to move between result pages.
Quick Start Guide
Step 1: Open the Alerts Dashboard
- Navigate to Alerts in the application sidebar.
- The alerts list will load. If none exist, you'll see a
Create Your First Alertprompt.
Step 2: Create a New Alert
- Click on the
Create Newbutton in the top-right. - Complete the modal form (see Managing Alerts for detailed steps).
- Click
Createon the final step to save.
Alert Types
The UI treats alerts as rule objects rather than fixed types, but you can express severity and intent via naming and webhook templates. Use the table below to map common use cases:
| Alert Type | Description | Use Case |
|---|---|---|
| Critical | Immediate attention required — use high-priority webhooks | System outages, data pipeline failures |
| Warning | Potential issues that need monitoring | Performance degradation, rising error rates |
| Informational | General status updates | Deployments, routine reports |
Note: The application does not enforce a fixed
Severityfield. Use naming conventions or webhook templates to communicate priority.
Common Use Cases
Monitor Failed Jobs
- Create an alert with
Filtersthat matchstatus=failedorlevel=errorfor a specificSelect Project. - Use a
Criticalwebhook template to notify on-call engineers.
Watch High Latency
- Use a numeric field in
Filterssuch asdata.duration>1000to trigger when latency exceeds a threshold. - Set a longer
Deduplication Periodto avoid repeated notifications.
Trigger on Specific Events
- Filter by
context.eventTypeequser_signupand point to an informational webhook for analytics pipelines.
Next Steps
See Manage Alert for step-by-step instructions on creating, viewing, editing, and deleting alerts.
Tip: Give alerts descriptive names and include the project name or severity in the
Alert Nameto make them easier to scan in the list.
Warning: Deleting an alert is permanent. Use the
Deleteaction only when you are sure the rule is no longer needed.