skills.rest
grafana
grafanaOFFICIAL
Explore all skills by this author →
Website𝕏@grafanaGitHub

debug

Correlate issue and session identifiers to trace execution failures in Symphony and Codex logs.

Updated Aug 27, 2026
Search Tags:#debugging#troubleshooting#logs#codex#error analysis#symphony
One-click install
npx skills add https://github.com/grafana/sigil --skill debug-grafana
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/grafana/sigil/tree/main/.agents/skills/debug
Command: npx skills add https://github.com/grafana/sigil --skill debug-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly identify the root cause of stuck runs, execution failures, and unexpected retries in Symphony and Codex by efficiently correlating logs using issue and session identifiers.

Core Features & Use Cases

  • Log Correlation: Links Linear issue identifiers to specific Codex sessions.
  • Root Cause Analysis: Isolates failures by tracing logs in the correct order.
  • Use Case: When a Symphony run is repeatedly failing or stalling, use this Skill to pinpoint the exact error message and context within the symphony.log files.

Quick Start

Use the debug skill to find logs related to issue identifier MT-625 in the symphony log files.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a stalled Symphony run using execution logs?▼

Debug stalled Symphony runs by analyzing the `symphony.log` files to isolate failure points. You can correlate issue and session identifiers to trace errors across log sources and classify problem types like orchestrator retry loops.

What is the best way to correlate Codex session identifiers with runtime errors?▼

Correlate Codex session identifiers by searching runtime logs to link specific issue identifiers to sessions. This isolates exact failure points and traces errors like application server failures or timeouts across the system.

How do I find the root cause of timeouts and application server failures in Symphony logs?▼

Find root causes of timeouts and application server failures by efficiently searching `symphony.log` files using tools like `rg`. This isolates specific error messages and classifies the problem type to pinpoint the exact failure context.

Does this log troubleshooting approach require specific search tools for Codex systems?▼

Yes, log troubleshooting for Codex systems requires efficient search tools like `rg` to isolate failure points within `symphony.log` files. Using `rg` allows you to quickly navigate large log sources and classify orchestrator retry loops.

Why does my Symphony orchestrator keep getting stuck in a retry loop?▼

Orchestrator retry loops occur due to execution failures or stalling within the Symphony system. You can investigate these stalled runs by correlating session identifiers in `symphony.log` to pinpoint the exact application server error causing the retries.

When should I use issue identifier correlation for troubleshooting execution failures?▼

Use issue identifier correlation when troubleshooting execution failures or unexpected retries in Symphony and Codex. Linking identifiers like Linear issues to specific sessions traces errors across log sources to isolate the root cause quickly.

Related Skills

Explore More Software Engineering Skills→
LuminairPrimeLuminairPrime

debug

Trace Symphony and Codex logs to resolve stuck runs and execution failures.

Community
Intermediate
Columbia-Cloudworks-LLCColumbia-Cloudworks-LLC
1

test-orchestrator

Automate Vitest test discovery, execution, and failure diagnosis in EquipQR projects.

Official
Advanced
ReinaMacCredyReinaMacCredy

debug

Analyze Symphony and Codex logs to trace AI agent run failures.

Community
Intermediate
asnar00asnar00
1

py-server-logs

Stream and search local or SSH-based Flask server logs.

Community
Intermediate