dashboard
El dominio dashboard tiene 1 acción. En la superficie meta se alcanzan todas a través de arcane_dashboard; 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 |
|---|---|---|
dashboard.get | Get dashboard snapshot | lectura |
Acciones
Sección titulada «Acciones»dashboard.get
Sección titulada «dashboard.get»Get dashboard snapshot
Returns the dashboard first-paint snapshot in a single response
- Tipo: lectura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_dashboardcon"action": "get" - Herramienta individual:
arcane_dashboard_get - Ruta de Arcane:
GET /api/environments/{id}/dashboard - ID de operación:
get-dashboard - Uso: Read-only first call for how one environment is doing (needs dashboard:read. environmentId is optional, from environment.list, defaulting to the configured environment): running/stopped/total container counts, image and volume in-use/unused counts, Arcane version info, and actionItems listing only the non-zero problems (stopped containers, pending updates of standalone containers and projects taken from stored update-check results, so run image_update.check_all first for fresh data, actionable unignored vulnerabilities, API keys expired or expiring within 14 days). includeTables defaults to true and adds up to 50 containers (newest first) and 50 images (largest first). Pass false for counters only, and leave debugAllGood unset because it forces an empty actionItems list. The snapshot is cached for about 5 seconds, so counts read right after a change may be stale. Drill down with container.list, image_update.summary or vulnerability.overview.
- Acciones relacionadas:
environment.list,container.list,image_update.summary,vulnerability.overview,image_update.check_all