Behind real time is how far Liquidsoap's output has slipped behind the clock since it started; it should sit near 0. Liquidsoap processes every output on one clock, so it can fall behind well before the machine's CPU is maxed out. Watch this and the speed rather than CPU alone.

What players actually get, read from the variant playlists. A smooth stream lands a new segment every target duration, so time between segments should run flat along the target line. A spike means players waited (past the dashed line, they likely stalled), a dip right after one is a catch-up burst, and gaps are encoder restarts. Renditions in step checks that every variant playlist ends on the same segment number.

The server runs as separate threads so the web pages can't hold up playout. Delay is how long work waited on that thread over the last 5 seconds (99th percentile, with the worst wait below it). A few milliseconds is normal; a high delay on the engine thread can make next-track answers and outbound streams late.

What each outbound actually handed to the network. For SRT, Total sent includes muxrate padding; Content is the audio and video inside it. With a muxrate set, total holds flat while content varies; a drop in total means the stream itself stalled.