Skip to main content

Documentation Index

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

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

Error rate spike detection monitors your daily request statistics and alerts you when the percentage of failed requests exceeds your configured threshold. It runs on a scheduled basis and evaluates error rates across organizations and individual users.

How it works

Each evaluation cycle:
  1. Queries yesterday’s request statistics from the request_stats_daily aggregate
  2. Sums total and failed requests across all endpoints for the target entity
  3. Calculates the error rate(failed / total) * 100
  4. Compares against your threshold — if the error rate exceeds threshold_percentage, an alert is triggered
A minimum of 10 requests is required to avoid noisy alerts from tiny sample sizes.

Configuration

You can configure error rate spike alerts from the Alerts page in your dashboard.
SettingDescriptionOptions
EnabledToggle the alert on or offtrue / false
Threshold PercentageError rate that triggers the alertAny positive number up to 100 (e.g., 10 for 10%)
ScopeWhat entities to monitororganization, user

Scope

  • Organization — monitors the aggregate error rate across all requests in your organization. All org admins, owners, and billing members receive the alert.
  • User — monitors the error rate across all requests made by your personal API keys.
Team and key-level scopes are not available for this alert type because the request_stats_daily aggregate does not include team or key identifiers.

Notifications

When an error rate spike alert fires, you are notified via your configured channels:
  • Email — includes the error rate percentage, total request count, failed request count, and a link to your usage page
  • SMS — a shorter summary with the same key figures
Each entity is subject to a 24-hour cooldown after an alert fires. During this window, no duplicate alerts are sent for the same entity.