Skip to content
Archive
← r/algotrading
1
100%
u/Negative_Resort_5832 3 days ago Strategy

how are you handling multi-source alerts without maintaining a whole event pipeline?

most of the monitoring I want to automate isn't actually trade execution. it's stuff like: a Polymarket contract moves quickly, BTC starts moving at the same time, and a related equity crosses some threshold. if all three happen within a certain window, send me an alert. doing any one of those is easy enough. once they're coming from different sources though, it turns into a much bigger engineering problem than I expected. with Python I end up needing to deal with ingestion, keeping state, stale/missing data, retries, duplicate alerts, then whatever I'm using for notifications. totally reasonable for something core to a strategy, but kind of annoying for monitoring ideas I might throw away a week later. TradingView + webhooks gets me part of the way, but not when half the condition lives somewhere TradingView doesn't see. I've been looking at the middle ground between those two approaches, including Alphio for defining some of the conditions in plain English. the part I'm still skeptical about is consistency rather than speed. if one source briefly disappears, two feeds disagree, or a condition stays true across multiple polling cycles, I want predictable behavior and not five alerts or some slightly different interpretation of the rule. for anyone running multi-source monitoring like this, where are you handling the state? inside your own event loop/database, or have you found a lighter setup that doesn't turn every alert into another small software project?
2 comments held Reddit says 0 on reddit ↗
  1. u/UntriedFormality_2 1 3 days ago
    the state problem is exactly where i burn out on side projects. you start with "i just want to know if X and Y happen together" and three days later you're debugging a redis instance at 2am i ended up keeping a tiny sqlite file with a handful of tables for active conditions, last-seen timestamps, and a dedup key. nothing fancy but it means i can kill the script and restart it without it forgetting what it already told me still feels like overkill for something i might abandon next tuesday though
  2. u/One-Next 1 3 days ago
    I mean yeah, of course you have to code to ingest data, process it and check your conditions and qualify a trade if all conditions are made. Why make it more complicated by adding other infrastructure? Do the whole thing in your application's memory. Track trades and fills in a db. Works fine for me.