Policies

Policy Actions

  • **Store**: Full write to the hot store. Every detail preserved.
  • **Rollup**: Aggregate into time-windowed counters. Saves storage while keeping trends.
  • **Sample**: Probabilistic storage at a configurable rate (0.0 to 1.0).
  • **Drop**: Discard the event. Only the usage counter increments.
  • Conditions

    Policies match events based on conditions: source, action, eventClass, importance, or subject. Operators include: equals, not equals, contains, starts with, and in (list match).

    Priority

    Policies are evaluated in priority order (lower number = higher priority). The first matching policy determines the action. If no policy matches, events are stored by default.

    Org-Level Budgets

    Each org can set a monthly event budget in **Settings**. When the budget is reached, events are automatically dropped unless their policy is explicitly set to store. This prevents runaway costs and keeps your event volume predictable.