Skip to content
Ankole

Read logs

When the Console only shows a failed request or an Agent does not reply, logs can show whether the failure is in the control plane, Worker, chat channel, or LLM Provider.

Ankole writes structured JSON logs by default. Each record has a severity, event name, message, and related context. Find the event first. Then use the Agent UID, Provider ID, or failure reason to narrow the records.

Get logs

Docker Compose:

docker compose logs --since 30m control-plane
docker compose logs --since 30m agent-computer-worker

Kubernetes:

kubectl -n ankole logs deployment/ankole-control-plane --since=30m
kubectl -n ankole logs deployment/ankole-agent-computer-worker --since=30m

Resource names can change with the release name. If the command cannot find an object, first run kubectl -n ankole get deployments.

Before you reproduce a problem, record the approximate time, Agent, chat channel, and user action. You can then inspect a small time window instead of reading from process startup.

Read one record

{
  "severity": "warning",
  "event": "signals_gateway.webhook.dispatch_failed",
  "message": "provider webhook dispatch failed",
  "handler_id": "lark",
  "reason": "..."
}
  • severity shows how serious the record is.
  • event is the best field for search and aggregation.
  • message gives a readable explanation.
  • Other fields identify the Agent, channel, Job, or request.

Warnings and information near an error often show the full sequence. Do not copy only the last line. Keep related records before and after the failure.

A useful search order

  1. Limit the logs to the time of the problem.
  2. Search for error, warning, or the error code from the Console.
  3. After you find the related event, filter by Agent UID, Provider ID, Worker ID, or chat adapter.
  4. Compare the records with the state under Console → Conversations or Background Agent Jobs.

Logs do not contain decrypted model credentials, channel secrets, or the Worker authentication key. Before you share logs for support, still check for user messages, URLs, and other business data.

Temporarily increase log detail

ANKOLE_LOG_LEVEL controls detail and uses info by default. To reproduce a difficult problem, you can temporarily set it to debug and restart the related service.

Restore the previous value after the reproduction to avoid a large continuing log volume.

ANKOLE_LOG_FORMAT can be json or pretty. If you use a log collection system, keep the format that it expects. See the deployment environment reference for all variables.

See the FAQ for checks organized by symptom.