Skip to main content

Configuring Alert Definitions

Alert Definitions are configured per strategy inside SMITH by the strategy author. They define what runtime behavior should emit an alert.

This page is about definitions (what gets emitted), not subscriptions (who receives it).

Why This Matters​

FORJ alerting has two halves:

  • Alert Definitions: strategy behavior → alert event
  • Alert Subscriptions: alert event → user/channel delivery

When a definition is matched at runtime, FORJ creates an AlertTrigger. Matching subscriptions then fan out into AlertDelivery records.

Setting Up Alert Definitions​

  1. In SMITH, open the Strategy Toolbar (gear icon).
  2. Select Configure Alerts.
  3. Add a new alert definition.
  4. Configure:
    • Kind — runtime behavior to watch (Event, Condition, Action, or Transition)
    • Trigger spec — specific target (for example: which action, which condition, or which transition)
    • Severity — importance level used later by subscription filters
    • Template — optional alert message format

Examples​

Alert on trade execution:

  • Kind: Action
  • Trigger spec: Execute Trade
  • Severity: High
  • Result: Strategy emits an alert whenever that action executes

Alert on state change:

  • Kind: Transition
  • Trigger spec: Any transition (or a specific from/to pair)
  • Severity: Medium
  • Result: Strategy emits an alert when state changes

Alert on condition failure:

  • Kind: Condition
  • Trigger spec: A specific condition name
  • Severity: Low
  • Result: Strategy emits an alert when that condition evaluates as configured

Next Step: Subscribe to Definitions​

After definitions are in place, users configure Alert Subscriptions to receive those alerts through in-app, email, SMS, or webhook.