Skip to main content
Alerts notify you when spending crosses a threshold. Set them once, and Fenra watches your costs 24/7.

​
How Alerts Work

  1. You define a threshold (e.g., “$1,000 in 24 hours”)
  2. Fenra monitors your spending continuously
  3. When the threshold is crossed, you get an email
No manual checking. No surprise bills at month-end.

​
Creating an Alert

  1. Go to Alerts in the navigation
  2. Click Create Alert
  3. Configure the alert:
  1. Click Create
Start with a higher threshold and lower it as you understand your typical spending patterns.

​
Time Periods

​
Filtering Alerts

Make alerts more targeted with filters:
  • By Model: Alert only when GPT-4 spending exceeds threshold
  • By Provider: Separate alerts for OpenAI vs. Anthropic
  • By Environment: Different thresholds for production vs. development
  • By Feature: Monitor specific high-cost features

​
Example: Production-Only Alert

To monitor only production spending:
  1. Set your threshold (e.g., $5,000)
  2. Add a filter: Environment = “production”
  3. Now staging and dev costs won’t trigger this alert

​
Alert Frequency

Control how often you’re notified:
Without throttling, a sustained overspend can flood your inbox. Enable throttling for high-frequency alerts.

​
Managing Alerts

​
Pause vs. Delete

  • Pause: Temporarily stop an alert. Turn it back on later.
  • Delete: Permanently remove it.
Pausing is useful during known high-spend periods (launches, migrations, etc.).

​
Editing

Click any alert to update its threshold, time period, filters, or recipients. Changes take effect immediately.

​
Alert History

See when alerts fired and why:
  • Timestamp of each trigger
  • Actual spend vs. threshold
  • Who was notified

​
Use Cases

Budget Guardrails

Alert at 50%, 75%, and 90% of monthly budget for early warnings.

Anomaly Detection

Set a low hourly threshold to catch unexpected spikes immediately.

Feature Monitoring

Watch specific high-cost features with targeted alerts.

Environment Separation

Higher thresholds for production, lower for development.

​
Best Practices

  1. Set multiple thresholds: 50%, 75%, 90% of budget gives progressive warnings
  2. Use filters: Generic alerts are noisy; targeted alerts are actionable
  3. Enable throttling: Avoid alert fatigue
  4. Review monthly: Adjust thresholds as your usage patterns change