Alert Skill

Create and manage metric alerts with automated notifications. Use this skill when users want to set up recurring monitoring: be alerted, notified, emailed, or warned about future metric changes. Supports threshold alerts (notify when a metric goes above or below a value) and anomaly-based alerts (set up ongoing monitoring for unusual patterns). Can create alerts from scratch or based on an existing visualization in the conversation. Handles notification channels (email, webhook), alert recipients, and attribute filters.

How It Works

The Alert skill provides tools for creating, updating, and managing metric alerts. When activated, the assistant can:

1. Search for metrics and attributes using semantic search
2. List available notification channels (email, webhook)
3. Create metric alerts with specified thresholds and conditions
4. Configure alert recipients and notification settings
5. Set up attribute filters to scope alerts to specific dimensions
6. Update existing alerts or change their state (enable/disable)

Alerts can be configured with date attributes for time-based filtering and can include multiple recipients and notification channels.

Examples

Creating a threshold alert:

User: "Alert me when monthly revenue drops below $50,000"
Assistant: [Creates alert with threshold condition, configures email notification]

Setting up anomaly monitoring:

User: "Monitor sales for anomalies and email me if anything unusual happens"
Assistant: [Creates anomaly-based alert, configures monitoring settings]

Creating alert from visualization:

User: [Shows revenue chart]
User: "Create an alert for this metric if it goes below the current value"
Assistant: [Extracts metric from visualization, creates alert with appropriate threshold]

Other use cases:

• “Alert me when revenue drops below $100,000”
• “Notify me if customer churn rate goes above 5%”
• “Email me if there are any unusual patterns in sales”
• “Warn me when there are anomalies in website traffic”

Limitations

• Alerts require appropriate workspace permissions
• Notification channels must be configured at the organization level
• Alert execution depends on scheduled automation runs
• Attribute filters must use compatible date attributes for time-based alerts