stream
El dominio stream tiene 1 acción. En la superficie meta se alcanzan todas a través de arcane_stream; en la individual, cada una es una herramienta propia; en la dinámica se ejecutan con arcane_execute_action y el ID canónico.
Resumen
Sección titulada «Resumen»| Acción | Título | Tipo |
|---|---|---|
stream.snapshot | Listen to Arcane’s live feed | lectura |
Acciones
Sección titulada «Acciones»stream.snapshot
Sección titulada «stream.snapshot»Listen to Arcane’s live feed
Listen to Arcane’s multiplexed live feed (environments, dashboard, activities, events, version) for a few seconds and return the events received
- Tipo: lectura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_streamcon"action": "snapshot" - Herramienta individual:
arcane_stream_snapshot - Ruta de Arcane:
GET /api/stream - ID de operación:
streamClient - Uso: Use to watch live state for a short window (seconds, default 5, max 120, stops early after maxEvents, default 100, and stopped says why it ended). For history use event.list or activity.list, and for one-off reads environment.list, dashboard.get or server.app_version. Each event’s data is an envelope with channel and one payload (environment, dashboard, activity, eventLog or version) carrying its own type: environments, dashboard and activities (one per environment, with environmentId) and version start with a type ‘snapshot’ of current state, but the events channel only sends eventLog type ‘changed’ with no event content, so follow it with event.list. Heartbeats (envelope type ‘heartbeat’, no channel) come every 15 s. Narrow channels (e.g. ‘environments,version’) to cut noise. Unknown channel names and channels the API key lacks permission for (dashboard, activities, events) are silently dropped, so a short window can return nothing, and limit caps activities per activities snapshot.
- Acciones relacionadas:
event.list,activity.list,environment.list,dashboard.get,server.app_version