Skip to main content
Logs capture what your agents, instances, and tasks do: their output and any errors. They are the first place to look when something does not behave as expected.

​
What is logged

​
Access

Logs are available in the Console under each resource — navigate to an agent, instance, or task and open its Logs tab. You can filter by time range and search by keyword.
Log retention varies by plan. Check the Console billing section for your organization’s retention period.
For structured debugging, correlate by request_id: when a Data Platform API call fails, the response includes a request_id in the error body. Match it in logs to find the exact failing operation.

​
Debugging workflow

When something fails, follow this sequence:
1

Identify the error

Capture the error response. Note the error_code and, for Data Platform errors, the request_id field in the response body.
2

Open logs for the resource

Navigate to the failing agent, instance, or task in the Console. Open its Logs tab. Filter to the time window of the failure.
3

Search by request_id

If you have a request_id, search for it in the log stream. This pinpoints the exact operation that failed and shows surrounding context (what happened before and after).
4

Check auto-logged signals

Agent instances automatically log startup, health check results, request latency, and recovery attempts. Look for health check failures or elevated latency immediately before the error.
5

Escalate with context

If the root cause isn’t clear, file a support ticket including: the error_code, request_id, environment_id, workspace_id, and the timestamp of the failure.

​
Log structure

Logs from your agent code appear as plain text lines. Structure them to make filtering easier:
Agent instances log the following automatically (you do not need to emit these):
  • Container startup and health check results
  • Requests received (method, path, latency)
  • Health check failures and recovery attempts

​
Common mistakes

  • Logging secrets from your agent. Never write credentials or tokens to output.
  • Looking only at the latest line. A failure’s root cause is often earlier in the log.

​
Best practices

  • Emit structured, meaningful log lines from your agent code.
  • Keep sensitive data out of logs.
  • Correlate logs with metrics and task events when debugging.

Metrics

Quantitative performance signals.

Runtime Lifecycle

Why an instance may be unhealthy.

Streaming & Replay

Real-time task visibility.

Troubleshooting

Resolve common issues.