The events a surface can be subscribed to by name alone.
Deliberately not every key of the event directory. A few entries are event
sources rather than collections — five in the shared base
(app.container_log_follow, app.stats, container.metrics,
filesystem.file_tail_follow, reporting.realtime), plus
virt.instance.metrics on v25.10 — and the directory marks them by giving
them a subscriptionParams model. They take arguments at subscribe time,
and how those arguments travel is not something the dump records:
core.subscribe is declared as params: [event: string], one string, with
no documented encoding for the rest.
So they are excluded rather than typed on a guess. Subscribing to one today
sends its name with the arguments dropped, which is not a subscription the
server can honour; a compile error naming the gap is more use than a stream
that stays silent. Widen this once the encoding is confirmed against a live
appliance — yarn live-check is the tool for that.
The events a surface can be subscribed to by name alone.
Deliberately not every key of the event directory. A few entries are event sources rather than collections — five in the shared base (
app.container_log_follow,app.stats,container.metrics,filesystem.file_tail_follow,reporting.realtime), plusvirt.instance.metricson v25.10 — and the directory marks them by giving them asubscriptionParamsmodel. They take arguments at subscribe time, and how those arguments travel is not something the dump records:core.subscribeis declared asparams: [event: string], one string, with no documented encoding for the rest.So they are excluded rather than typed on a guess. Subscribing to one today sends its name with the arguments dropped, which is not a subscription the server can honour; a compile error naming the gap is more use than a stream that stays silent. Widen this once the encoding is confirmed against a live appliance —
yarn live-checkis the tool for that.