subwave-log-analysis

Generate diagnostic reports from SUB/WAVE event logs by traceId.

1.2k|104|Updated May 11, 2026
One-click install
npx skills add https://github.com/perminder-klair/subwave --skill subwave-log-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subwave-log-analysis
Source: https://github.com/perminder-klair/subwave/tree/main/.claude/skills/subwave-log-analysis
Command: npx skills add https://github.com/perminder-klair/subwave --skill subwave-log-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SUB/WAVE operators need to understand what the radio is doing at runtime—especially when it’s slow, repetitive, or malfunctioning—without manually parsing large JSONL log files.

Core Features & Use Cases

  • Unified event-log diagnostics: Translates state/logs/events-*.jsonl into a structured diagnostic report focused on Navidrome usage, picker/DJ quality, and health anomalies.
  • Actionable operational recommendations: Interprets log patterns and pairs findings with concrete knob-turning recommendations (e.g., pool breadth, LLM/provider issues, Navidrome URL misrouting).
  • Trace-grounded root cause analysis: Uses shared traceId to help connect symptoms to the specific decisions and API calls that caused them.

Use this when you want to answer questions like “analyse the subwave logs”, “check the radio’s behaviour”, “why does it keep playing the same artists”, “is the station healthy”, or “how are the Navidrome calls looking”.

Quick Start

Ask: analyse the subwave logs for the last 24 hours using the SUB/WAVE state directory.

Frequently Asked Questions about subwave-log-analysis

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

FAQPage Schema
How do I diagnose Navidrome latency issues from JSONL event logs?

To diagnose Navidrome latency from JSONL event logs, aggregate traces by `traceId` to connect API call delays with specific picker decisions. This log analysis identifies slow Subsonic API responses and translates raw event files into actionable runtime latency reports.

Why does my Navidrome radio keep playing the same artists?

Repetitive artist selection in Navidrome radio is caused by limited picker pool breadth. Analyzing unified event logs traces DJ decisions by `traceId`, revealing patterns in music recommendation logic and providing concrete knob-turning recommendations to widen the selection pool.

What is the best way to audit radio operations and check station health?

Auditing radio operations and checking station health is best done by parsing `state/logs/events-YYYY-MM-DD.jsonl` files. This diagnostic process aggregates daily event logs into a structured report showing health anomalies, Navidrome usage, and picker quality over recent windows.

Can I debug Navidrome connection failures and tool errors from runtime logs?

Yes, you can debug Navidrome connection failures and tool errors from runtime logs by reading JSONL event files and grouping entries by `traceId`. This log analysis identifies URL misrouting and LLM provider issues, pairing health anomalies with specific failed API calls.

Do I need a specific state directory structure for SUB/WAVE log analysis?

Yes, SUB/WAVE log analysis requires accessing the `state/logs/` directory containing `events-YYYY-MM-DD.jsonl` files. The diagnostic script reads these specific JSONL log formats to aggregate traces by `traceId` and generate grounded runtime audit reports without manual re-derivation.