Trading Analytics Dashboard

Built: March 5, 2026 (Midday autonomous build)

What It Does

Surfaces historical insights from the investment system that the main trading dashboard doesn't show:

📈 Signal Generation Trends

• Chart showing daily signal counts over time
• Helps identify if momentum scanner is too conservative
• Current insight: 0 signals for 3+ days (Mar 3-5) - potential threshold issue

⚠️ Data Quality Monitor

• Surfaces API errors and ticker issues
• Current issue: SQ (Square) showing as "delisted" - ticker may have changed (Block rebrand)
• Track data feed problems

🚫 Order Failure Tracking

• Documents blocked/rejected orders
• Today's example: COIN order blocked with "no market data" warning
• Help diagnose IBKR integration issues

📊 Performance Insights

• Summary stats: total signals, avg/day, error counts
• Recommendations for system improvements

How It Works

Data Pipeline

1. Log Parser (parse_trading_logs.py):

   • Reads /home/ubuntu/clawd/investment/logs/orchestrator.log
   • Extracts signal counts, errors, order status
   • Outputs trading_analytics.json

2. Dashboard (Next.js):

   • Loads analytics JSON
   • Visualizes with Recharts
   • Provides actionable recommendations

Auto-Update Process

The log parser should run periodically (e.g., hourly cron) to keep data fresh:

# Add to cron or run manually
python3 /home/ubuntu/clawd/builds/midday/2026-03-05/parse_trading_logs.py

Then commit and push the updated JSON file to auto-deploy.

Tech Stack

• Frontend: Next.js 15, TypeScript, Tailwind CSS
• Charts: Recharts
• Deployment: Vercel (static export)
• Data: Python log parser → JSON

Local Development

npm install
npm run dev
# Open http://localhost:3000

Build & Deploy

npm run build
# Outputs to /out directory (static site)

Key Insights (as of Mar 5)

1. Signal Drought: No signals generated Mar 3-5 (3 days)

   • Momentum scanner may need threshold adjustment
   • Market conditions not meeting criteria

2. SQ Ticker Error: 1,759 "delisted" errors for $SQ

   • Square rebranded to Block
   • Need to update ticker or remove from watchlist

3. Missing Order Failure Tracking:

   • COIN order blocked today but not logged
   • Implement order rejection logging in trading agents

Next Steps

1. Set up hourly cron to regenerate analytics
2. Add order failure logging to trading system
3. Fix SQ ticker issue (update to BLOCK or remove)
4. Review momentum scanner thresholds

---

Complements: Trading Dashboard (current portfolio state) Purpose: Historical analysis & system diagnostics