Skip to main content

Configuring Alert Definitions

Alert definitions are configured per strategy inside SMITH. They define which runtime behavior should emit an alert trigger when the strategy runs.

This page covers alert definitions only. Delivery is handled separately through Alert Subscriptions.

Definitions vs subscriptions​

  • Alert definitions answer: "what should emit an alert?"
  • Alert subscriptions answer: "who should receive it, and through which channels?"

When a definition matches at runtime, FORJ creates an alert trigger. Matching subscriptions then fan out into delivery records.

Open the alert definitions panel​

  1. Open a strategy in SMITH.
  2. Open the Strategy Toolbar.
  3. In Trade & Alerts, select Manage Strategy Alert Definitions.
  4. Click New alert.

The alert wizard​

The editor is a four-step wizard:

  1. General Info
  2. Trigger
  3. Channels
  4. Review

Step 1: General Info​

In General Info, you define the metadata for the alert definition:

  • Name
  • Severity
  • Visibility
  • Description (optional)

There is no template step in the current editor.

Step 2: Trigger​

In Trigger, you decide what runtime behavior should fire the alert. There are four trigger kinds:

Transition​

Use this when you want an alert when the strategy moves between states.

  • Choose Any transition, or
  • choose one specific transition by its source -> target pair.

Guard​

Use this when you want an alert around guard evaluation.

  • Select Any guard, or a specific guard.
  • Then choose When:
    • Guard evaluated (any result)
    • Guard passes
    • Guard fails

Action​

Use this when you want an alert when an action executes.

You can target:

  • Any action
  • Any Execute Trade
  • one specific action

If an action contains an Execute Trade step, the editor shows that in the action picker.

Event​

Use this when you want an alert on incoming or platform-level events.

The event picker is grouped into:

  • Stream Arrival Events
  • Trade Lifecycle
  • Scheduled Timers
  • Platform Events

Depending on the event, you can also add optional filters:

  • Market data type
  • Data stream filter
  • Trade plan filter for trade-plan lifecycle events

Step 3: Channels​

In Channels, you choose which delivery channels this definition is allowed to use.

  • In-App is always available.
  • Email, SMS, and Webhook depend on workspace plan features.
  • Subscribers can only use channels allowed by the definition.

Step 4: Review​

The Review step summarizes:

  • name
  • severity
  • visibility
  • trigger type
  • allowed channels

Save the draft from the panel footer when the definition is valid.

Practical examples​

Alert on any trade execution​

  • Trigger type: Action
  • Action: Any Execute Trade
  • Channels: In-App + Email

Alert when a specific guard fails​

  • Trigger type: Guard
  • Guard: your named guard
  • When: Guard fails

Alert when the strategy moves into a position state​

  • Trigger type: Transition
  • Transition: select the specific Watching -> InPosition transition