Alerts notify you when spending exceeds a threshold. Set them up once, and Fenra monitors your costs 24/7.
Creating an Alert
- Go to Alerts in the navigation
- Click Create Alert
- Configure:
| Setting | What to Enter |
|---|
| Name | Descriptive name (e.g., “Daily Budget Alert”) |
| Threshold | Dollar amount that triggers the alert |
| Time Period | Hour, day, week, or month |
| Filters | Optional: specific models, environments, features |
| Recipients | Who gets notified |
- Click Create
Time Periods
| Period | Best For |
|---|
| Last Hour | Catching sudden spikes |
| Last 24 Hours | Daily budget monitoring |
| Last 7 Days | Weekly reviews |
| Last 30 Days | Monthly budgets |
Filtering Alerts
Make alerts more targeted:
- By Model: Only GPT-4 or only Claude
- By Environment: Only production
- By Feature: Only specific features
Example: Production-Only Alert
- Set threshold to $5,000
- Add filter: Environment = “production”
- Staging/dev costs won’t trigger it
Alert Frequency
| Option | Behavior |
|---|
| Immediate | Alert as soon as threshold is crossed |
| Throttled | Max one alert per hour/day |
Enable throttling to avoid inbox flooding during sustained overspend.
Managing Alerts
- Pause: Temporarily disable without deleting
- Edit: Update threshold, filters, or recipients
- Delete: Permanently remove
Examples
Multi-Threshold Budget Alert
Set three alerts for progressive warnings:
| Alert | Threshold | Purpose |
|---|
| Budget 50% | $5,000/month | Early warning |
| Budget 75% | $7,500/month | Yellow flag |
| Budget 90% | $9,000/month | Red flag |
Feature-Specific Alert
Monitor a high-cost feature:
- Threshold: $500/day
- Filter: feature_name = “image-generation”
- Recipients: Product and engineering leads
Best Practices
- Start conservative: Higher thresholds at first, lower as you learn patterns
- Use multiple thresholds: 50%, 75%, 90% of budget
- Filter appropriately: Generic alerts are noisy
- Enable throttling: Avoid alert fatigue
- Review monthly: Adjust as usage patterns change
Next Steps
