who drives
Either way every session stays individually addressable: an autonomous session can still be opened, paused by hand, or silenced. The mode decides who acts, not whether you can.
content
no matches — is the catalogue loaded?
Required, and resolved against the catalogue server-side — the video_type the graph filters on comes from the catalogue row, not from this page.
session metadata
Free-form, and written verbatim into events_raw — these are the columns the live graph filters on. Create a second batch with a different value to have something to filter between.
how many, how often
steady rate
6.7/s
mode
manual
events total
24,000
live now
0
headroom
10,000
pick content first
what happens next
- Start and Play are written at the same instant, so every session is active immediately.
- Each session then heartbeats on its own at the cadence, with the first tick staggered across it so the insert rate is flat rather than a spike.
- On the sessions page you can pause, background, silence or end any one of them.
- Each session then holds its state until you change it.
- After 60 minutes each session ends itself with a real
VideoSessionEnd, so a fleet left running stops on its own. - State is written to
fleet_sessions, so a restart restores the fleet rather than losing it while its events stay inevents_raw.
Events go to events_raw through the same ingest path a real producer uses, so nothing here is a shortcut around validation or deduplication.