Log Analysis with Claude Code: API Runtime Pattern
A production playbook for log analysis in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Platform and support teams
The problem
Platform and support teams need log analysis to run repeatedly against application logs, traces, metrics exports, and incident notes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the log analysis instructions as a skill, send application logs, traces, metrics exports, and incident notes as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For log analysis, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=log-analysis
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo