A mapped reference for exception tracking — how it runs, how to configure it, and where it runs aground under load.
Mechanics
The mechanics of exception tracking form one pipeline: raw market data in, computed signal out, decision routed to the order engine.
Waypoints (Configuration)
Configuring exception tracking comes down to a short list of parameters. Vendor defaults fit demonstrations; live deployment deserves its own pass.
Wreck Record (Failure Modes)
exception tracking sinks in recognizable ways: silent feed gaps, parameters no longer matching the market, latency spikes at the worst moment.
Navigation Checks (Evaluation)
Evaluate exception tracking on measured outcomes — return distribution, drawdown depth, operational burden — never on one lucky stretch.
Configuration Reference
# Exception Tracking tested configuration mode: production timeframe: auto risk_limits: max_drawdown: 15 percent max_position: 3 percent monitoring: alert_threshold: 0.5 report_interval: hourly
Parameter Impact
| Parameter | Effect | Trade-off |
|---|---|---|
| timeframe | Signal frequency | Higher means fewer but more reliable signals |
| risk_limit | Maximum exposure | Lower means safer but slower returns |
| lookback | Indicator sensitivity | Longer means smoother but lagging |