event

The event domain has 4 actions. On the meta surface they are all reached through arcane_event; on the individual surface each one is its own tool; on the dynamic surface run them with arcane_execute_action and the canonical ID.

Summary

Action	Title	Kind
event.delete	Delete an event	destructive
event.list	List events	read
event.list_by_environment	Get events by environment	read
event.stats	Event severity counts	read

Actions

event.delete

Delete an event

Delete a system event by ID

• Kind: destructive — requires confirm: true
• Required parameters: eventId
• Meta tool: arcane_event with "action": "delete"
• Individual tool: arcane_event_delete
• Arcane route: DELETE /api/events/{eventId}
• Operation ID: deleteEvent
• Usage: 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.
• Related actions: event.list, event.list_by_environment

event.list

List events

Get a paginated list of system events

• Kind: read
• Required parameters: none
• Meta tool: arcane_event with "action": "list"
• Individual tool: arcane_event_list
• Arcane route: GET /api/events
• Operation ID: listEvents
• Usage: 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.
• Related actions: 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

• Kind: read
• Required parameters: environmentId
• Meta tool: arcane_event with "action": "list_by_environment"
• Individual tool: arcane_event_list_by_environment
• Arcane route: GET /api/events/environment/{environmentId}
• Operation ID: getEventsByEnvironment
• Usage: 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.
• Related actions: environment.list, event.list, event.delete

event.stats

Event severity counts

Get global event counts grouped by severity

• Kind: read
• Required parameters: none
• Meta tool: arcane_event with "action": "stats"
• Individual tool: arcane_event_stats
• Arcane route: GET /api/events/stats
• Operation ID: getEventStats
• Usage: 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.
• Related actions: event.list, event.list_by_environment