event

El dominio event tiene 4 acciones. En la superficie meta se alcanzan todas a través de arcane_event; 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

Acción	Título	Tipo
event.delete	Delete an event	destructiva
event.list	List events	lectura
event.list_by_environment	Get events by environment	lectura
event.stats	Event severity counts	lectura

Acciones

event.delete

Delete an event

Delete a system event by ID

• Tipo: destructiva — exige confirm: true
• Parámetros obligatorios: eventId
• Meta-herramienta: arcane_event con "action": "delete"
• Herramienta individual: arcane_event_delete
• Ruta de Arcane: DELETE /api/events/{eventId}
• ID de operación: deleteEvent
• Uso: Permanently removes one entry from the event log. eventId is the id of an item from event.list or event.list_by_environment. Needs the events delete permission, and an unknown ID fails with 404 “event not found”. Old events are already purged automatically after 36 hours, so this is only for removing a specific entry.
• Acciones relacionadas: event.list, event.list_by_environment

event.list

List events

Get a paginated list of system events

• Tipo: lectura
• Parámetros obligatorios: ninguno
• Meta-herramienta: arcane_event con "action": "list"
• Herramienta individual: arcane_event_list
• Ruta de Arcane: GET /api/events
• ID de operación: listEvents
• Uso: Arcane’s recorded events across all environments (container started, image pulled, project deployed, user logged in, webhook triggered…), each with id, type, severity (info, success, warning, error), title, resource, username, environmentId and timestamp. The event-cleanup job deletes events older than 36 hours, so this is recent history only. Filter with severity (comma-separated for several), type (comma-separated: a value with a dot such as container.start is exact, one without such as container matches the whole category) and search (matches title, description, resource name and username). Pass sort=timestamp with order=desc for newest first, since without a valid sort column the order is by random event ID. Paginate with start and limit (default 20, capped at 100, -1 returns all). Use event.list_by_environment for one environment and activity.list for one environment’s background tasks and their progress.
• Acciones relacionadas: event.list_by_environment, event.stats, event.delete, activity.list

event.list_by_environment

Get events by environment

Get a paginated list of events for a specific environment

• Tipo: lectura
• Parámetros obligatorios: environmentId
• Meta-herramienta: arcane_event con "action": "list_by_environment"
• Herramienta individual: arcane_event_list_by_environment
• Ruta de Arcane: GET /api/events/environment/{environmentId}
• ID de operación: getEventsByEnvironment
• Uso: Same filters, sorting, pagination and result as event.list, but only events whose environmentId matches. environmentId (from environment.list) is required and has no default. Events not tied to an environment, such as user logins, never appear here, so use event.list for those.
• Acciones relacionadas: environment.list, event.list, event.delete

event.stats

Event severity counts

Get global event counts grouped by severity

• Tipo: lectura
• Parámetros obligatorios: ninguno
• Meta-herramienta: arcane_event con "action": "stats"
• Herramienta individual: arcane_event_stats
• Ruta de Arcane: GET /api/events/stats
• ID de operación: getEventStats
• Uso: Takes no parameters and returns global counts of stored events (all environments, last 36 hours of retention) as total, info, success, warning and error, for a quick check whether errors are piling up. To see the events behind a count, call event.list with severity set.
• Acciones relacionadas: event.list, event.list_by_environment