swarm_task
The swarm_task domain has 1 action. On the meta surface they are all reached through arcane_swarm_task; 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
Section titled “Summary”| Action | Title | Kind |
|---|---|---|
swarm_task.list | List swarm tasks | read |
Actions
Section titled “Actions”swarm_task.list
Section titled “swarm_task.list”List swarm tasks
- Kind: read
- Required parameters: none
- Meta tool:
arcane_swarm_taskwith"action": "list" - Individual tool:
arcane_swarm_task_list - Arcane route:
GET /api/environments/{id}/swarm/tasks - Operation ID:
list-swarm-tasks - Usage: Every task in the swarm, including ones that have stopped or failed (a task is one service replica on a node). Each item has serviceName, nodeName, desiredState, currentState, error and containerId. The environment must be a swarm manager. Otherwise the call fails. search matches task name, service name, node name, task ID or current state (for example a service name or “running”). sort accepts service, node, state, created or updated. Paginated with start/limit (default 20). To list the tasks of one known service, node or stack, use swarm_service.tasks, swarm_node.tasks or swarm_stack.tasks instead.
- Related actions:
swarm_service.tasks,swarm_node.tasks,swarm_stack.tasks,swarm_service.logs,swarm.status