Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.duckie.ai/llms.txt

Use this file to discover all available pages before exploring further.

Alerts notify you when important metrics cross thresholds, so you can respond quickly to issues.

What are Alerts?

Alerts are automated notifications triggered by metric conditions:
  • Escalation rate exceeds threshold
  • Response time degrades
  • Error rate spikes
  • Volume anomaly detected

Creating Alerts

1

Navigate to Alerts

Go to Analyze → Alerts.
2

Click Create Alert

Click Create Alert.
3

Select Metric

Choose what to monitor:
  • Escalation rate
  • Resolution rate
  • Response time
  • Error rate
  • Volume
4

Set Condition

Define when to trigger:
  • Threshold value
  • Duration (sustain for X minutes)
  • Comparison (above, below, change)
5

Configure Notification

Choose how to be notified:
  • Email
  • Slack
  • Webhook
6

Save

Save and activate the alert.

Alert Conditions

Threshold Alerts

Trigger when a metric crosses a value:
ConditionExample
AboveEscalation rate > 25%
BelowResolution rate < 70%
ChangeVolume increased > 50%

Duration

Require the condition to persist:
Escalation rate > 25% for 10 minutes
This prevents alerting on brief spikes.

Scope

Apply to specific deployments:
  • All deployments
  • Specific deployment
  • Specific channel

Example Alerts

High Escalation Rate

SettingValue
NameHigh Escalation Alert
MetricEscalation rate
ConditionAbove 25%
Duration10 minutes
NotificationSlack #support-alerts

Degraded Response Time

SettingValue
NameSlow Response Alert
MetricResponse time P95
ConditionAbove 30 seconds
Duration5 minutes
NotificationEmail + Slack

Volume Spike

SettingValue
NameVolume Anomaly
MetricConversation volume
Condition2x normal for time of day
NotificationSlack #support-team

Resolution Drop

SettingValue
NameLow Resolution Alert
MetricResolution rate
ConditionBelow 60%
Duration1 hour
NotificationEmail

Notification Channels

Email

  • Send to specific addresses
  • Include alert details and links
  • Configure frequency (immediate, digest)

Slack

  • Post to a channel
  • Direct message
  • Include actionable links

Webhook

  • POST to your endpoint
  • Include alert data as JSON
  • For custom integrations

Managing Alerts

Active Alerts

View currently triggered alerts:
  • What triggered
  • When it started
  • Current value

Alert History

See past alerts:
  • When triggered
  • How long it lasted
  • When resolved

Edit/Disable

Modify existing alerts:
  1. Click on the alert
  2. Edit settings
  3. Save changes
Or disable temporarily:
  1. Toggle status to disabled
  2. Alert won’t trigger
  3. Re-enable when ready

Responding to Alerts

When an alert triggers:
1

Acknowledge

Note that you’ve seen the alert.
2

Investigate

Go to run history or metrics to understand the issue.
3

Take Action

Fix the underlying problem.
4

Verify

Confirm the metric has recovered.

Best Practices

Start Simple

Begin with critical alerts only:
  • High escalation rate
  • Error spikes
  • Major volume anomalies
Add more as needed.

Set Appropriate Thresholds

Avoid alert fatigue:
  • Too sensitive = too many alerts
  • Too loose = miss real issues
  • Start conservative, adjust based on experience

Use Duration

Require sustained conditions:
  • Prevents alerting on momentary blips
  • Focus on real problems
  • Reduce noise

Route to Right People

Send alerts where they’ll be acted on:
  • Operations team for volume spikes
  • Engineering for error rates
  • Support leads for escalation issues

Next Steps

Performance Metrics

Understand metrics to alert on

Run History

Investigate alert causes