obs: icecast log volume — ~75% is per-metadata-update ceremony; curate before it drowns Drilldown

[genwave-radio]

📈 Measured 2026-07-29 (Loki, demo): icecast went from ~8 lines/hour to ~650–790 lines/hour at the v2.8.6 deploy — i.e. the moment gh-#115/PR #222 started streaming its logs. The feature works; the volume is uncurated.

Breakdown (3h sample, 2,000 lines):

• ~25% access-log lines — the valuable ones (listener connect/disconnect with duration, mount hits — Ship icecast access/error logs to Loki #115's acceptance).
• ~75% is one repeating 8-line ceremony per liquidsoap metadata push (~every 70s with patter cycles): admin_handle_request · WARN admin_enforce_unsafe (legacy source uses GET) · WARN command_metadata ("song" + "artist"/"title" both present) · 2× command_metadata INFO · 2× util_conv_string INFO · 2× event_stream_queue INFO.

Fix options, with caveats:

1. Alloy drop stage (genwave-infra repo) — drop the six ceremony patterns at ingest. ✅ Keeps 100% of access-log + listener/source visibility + real errors; cuts ~70% of volume. ⚠️ Lives in the infra repo, not here; pattern list needs maintaining if icecast wording changes on upgrade.
2. loglevel 3→2 (warn) in icecast.xml.tmpl — ships with a release. ✅ One-line repo change. ⚠️ Loses the listener count now N INFO lines (listener visibility survives via the access log) and the 2 WARN-level ceremony lines per update remain (~40/h).
3. Engine-side trim: send only song= (not artist/title alongside) in the ICY update from genwave.liq to silence one WARN per update. ⚠️ Micro-win only; touches the on-air metadata path for a log line.
4. Do nothing — ~18k lines/day is cheap for Loki; the cost is Drilldown signal-to-noise, not storage.

Recommendation on record: option 1 first, option 2 later if the WARN residue still annoys. Decision deferred — fold into the gh-#153 logging audit rather than one-off. Related: #115, PR #222, #153.

[genwave-radio]

📊 Quantified in the 2026-07-30 LLL, and it's worse than 75%: the new icecast image (v2.8.8 pin set, onset 07-29 ~11:00 MDT, zero before) emits two WARNs per metadata push, ~230 lines/hour, ~5,500/day — now the single largest log source on the station by an order of magnitude (fleet error/warn baseline was ~zero).

The pair, every push:

• admin/admin_enforce_unsafe … uses safe method GET on /admin/metadata — Icecast 2.5 flagging Liquidsoap's legacy GET-based metadata update. This one's also a forward-compat signal: upstream is telegraphing that GET on admin endpoints is on the way out.
• admin/command_metadata Metadata request mountpoint /stream contains "song" but also "artist" and/or "title" — our push sends redundant fields.

Push cadence is also interesting: bursts of ~4 pushes over ~20s per track boundary (crossfade sources re-pushing?), not 1 per track — so there's a volume lever on our side too, beyond Alloy-stage curation.

[genwave-radio]

📊 Day-scale verification (LLL 2026-08-12 evening) — the drop is working at day scale, with one residual shape.

Confirmed collapse: icecast log volume went 17.7k → 7.3k lines/day (08-11 vs 08-12, full-day windows).

Residual shape the 5 pinned expressions miss — still shipping ~60/h (~1.4k/day):

INFO admin/command_metadata Metadata (url) on mountpoint /stream changed to "https://demo.genwaveradio.com/spectator/api/artwork/station"
INFO admin/command_metadata Metadata (url) on mountpoint /stream changed to "https://demo.genwaveradio.com/spectator/api/artwork/8808cb2463d18697020200e47d410d49"

It's the Metadata (url) artwork variant — fires on every artwork-url push (~1/min), distinct from the Metadata (song) sentences the drop pins. If we want the "~0" originally scoped here, it needs a 6th stage.match/stage.drop expression in genwave-infra, sentence-scoped the same way (match the Metadata (url) on mountpoint … changed to "…/spectator/api/artwork/ sentence, not blanket command_metadata, so real ERRORs stay).

Rate history: ~323/h pre-drop hour → ~60/h steady since 08-11 23:00Z — so the applied drop cut ~80%; this variant is all that remains.