DROP ALERT NOTES
How to change min_drop without losing alerts
min_drop is set per connection, so changing it means reconnecting, and the stream replays nothing. The quiet-window procedure that keeps the gap empty.
Changing min_drop is a small config edit with a hidden cost: the threshold lives on the connection, so applying it means closing the stream and opening a new one, and the documentation promises no resume point. Anything that falls between the close and the open is missed unless you plan for it. Here is the procedure that changes the threshold and keeps the record complete.
Understand the gap you are creating
The stream does not replay: alerts that fall while you are disconnected are simply not delivered later, as the SSE setup guide states, checked 2026-10-07. A threshold change is therefore a planned outage, and the goal is to make it a short and well-timed one.
Two numbers decide how much the change costs: how long the reconnect takes, and how busy the markets are while it happens. Both are yours to choose by picking the moment.
Pick the quietest window you can find
Schedule the change for the quietest stretch of the week for your sports: mid-morning midweek for soccer, overnight for whichever league drives your alerts. The live vs prematch page covers how different the two rhythms are, and prematch boards in quiet hours can go minutes between drops, which is exactly the cover you want.
Closing and reopening inside one quiet minute usually costs nothing at all.
Backfill from the REST drops endpoint
For anything that did fall in the gap, the recovery path is the REST drops endpoint, which keeps recent drops for a few hours with a timestamp on each, per the setup guide. After the new connection is up, pull the drops for the window you were down, run them through the same filter and dedupe rules as the stream, and your record is whole again.
One caution: run the backfill through the old threshold or the floor, not the new one, so the gap window is judged the same way as the minutes around it. Apply the new threshold from the moment the new connection opens.
Log the change as an event
Write one line: old threshold, new threshold, the time, and the gap you backfilled. Your alert log now has a clean boundary, and any week-over-week comparison of alert counts knows the rate changed because the rule did, not the market.
The drop alerts guide covers choosing the threshold itself; the work above is what makes the changeover invisible in your data.
Quiet window, close, reconnect, backfill, log. Five steps and the threshold changes without losing a single move.