claude-live-logs

To analyze Claude Code live execution logs in Elasticsearch, query the logs-claude.otel-default and agent-events indices using a specific task_id, pipeline_run_id, or agent_name. This returns structured fields like timestamp, event_type, and pipeline_run_id for diagnosis.

Monitoring recent Claude Code agent activity in Elasticsearch involves querying the agent-events index with an optional recent activity time window. This provides near real-time visibility into tool results and API calls for quick performance tuning.

Diagnosing pipeline run issues with Claude live logs requires querying Elasticsearch by pipeline_run_id to cross-correlate agent lifecycle events and OTEL logs. This contextual timeline of tool results isolates specific failures within the pipeline execution.

Searching Claude Code execution logs requires access to specific Elasticsearch indices: logs-claude.otel-default and agent-events. These indices store the structured fields, such as event_type and agent_name, needed to centralize debugging and performance analysis.

You can query Claude Code logs by agent_name in Elasticsearch to troubleshoot errors and inspect specific runs. This filters the live execution logs to display contextual timelines of tool calls and API usage relevant to that agent.

Querying Claude live logs in Elasticsearch returns structured fields including timestamp, event_type, agent_name, and pipeline_run_id. These fields enable cross-resource correlation between agent lifecycle events and OTEL logs for pipeline troubleshooting.