Alert Rules
Alert rules notify you when error volume crosses a threshold. Get notified via email, Slack, Discord, or a webhook when things go wrong, without watching the dashboard all day.
Creating a rule
Go to Settings > Alerts and click New Rule.
Rule options
| Field | Description |
|---|---|
| Project | Which project to watch |
| Environment | Scope to a specific environment, or leave blank for all |
| Condition | The trigger (see below) |
| Threshold | The value that triggers the alert |
| Interval | How often to evaluate the condition (e.g., every 5 minutes) |
| Action | Email, Slack, Discord, or webhook |
Conditions
| Condition | What it checks |
|---|---|
| Error count | Total events in the last interval exceeds the threshold |
| New issue | A brand new issue fingerprint is seen |
| Issue regression | A resolved issue re-opens |
Email alerts
Enter one or more email addresses in the alert action. Tindra sends a plain-text email with a link to the issue or issues that triggered the alert.
Email requires an EMAIL_PROVIDER to be configured on your instance. See Configuration.
Slack alerts
Select Slack as the action type and paste an incoming webhook URL. You can create one in your Slack workspace under Apps > Incoming Webhooks.
Tindra sends a formatted message with the rule name, trigger, project, and a direct link to the issue.
Discord alerts
Select Discord as the action type and paste an incoming webhook URL. You can create one in Discord under Channel Settings > Integrations > Webhooks.
Tindra sends a formatted message with the rule name, trigger, project, and a direct link to the issue.
Webhook alerts
Enter a URL and Tindra will POST a JSON payload when the rule fires:
{
"rule_id": "550e8400-e29b-41d4-a716-446655440000",
"rule_name": "High error rate on /api/orders",
"project_id": "proj_abc123",
"project_name": "my-app",
"trigger": "event_count",
"fired_at": "2024-11-15T14:32:00Z",
"details": {
"event_count": 47,
"threshold": 20,
"window_mins": 15
},
"issues": [
{ "id": "iss_xyz", "title": "TypeError: Cannot read 'id' of null", "level": "error" }
]
}
The trigger field is one of: new_issue, regressed, new_or_regressed, event_count.
Webhooks are delivered once per trigger. Tindra does not retry failed deliveries. If your endpoint is temporarily unavailable, you will miss that notification.
Alert fatigue
Start with a high threshold and a low-frequency interval. An alert that fires every five minutes stops getting read. A weekly digest of persistent issues is often more actionable than a constant stream of individual notifications.
Good defaults to start with:
- Error count > 50 in 15 minutes for production
- New issue in production (immediately)
- Issue regression (immediately)