daq-logs

Query SQLite DAQ log errors with read-only SQL joins.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/carbonscott/deploy-opencode --skill daq-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daq-logs
Source: https://github.com/carbonscott/deploy-opencode/tree/main/claude/skills/daq-logs
Command: npx skills add https://github.com/carbonscott/deploy-opencode --skill daq-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quickly locate, analyze, and trace errors in the LCLS DAQ log database to diagnose issues and understand failure cascades.

Core Features & Use Cases

  • Read-only access to the DAQ logs database stored as SQLite, enabling precise searches across log_files and log_errors.
  • Support for identifying error cascades by pulse_id, host, component, or timestamp, and for validating ingestion status.
  • Real-world use: diagnose a surge of daq errors by pulsing through logs to pinpoint the root cause and affected components.

Quick Start

Run a read-only SQL query to fetch recent errors for a given host and component and output results with headers.

Frequently Asked Questions about daq-logs

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

FAQPage Schema
How do I query LCLS DAQ logs to trace error cascades by pulse_id?

Query LCLS DAQ logs by running read-only SELECT statements that join log_files and log_errors tables to trace error cascades by pulse_id. You can filter by host, component, or timestamp and order results to pinpoint root causes.

What is the best way to investigate DAQ log errors stored in a SQLite database?

Investigate DAQ log errors in a SQLite database by executing SQL queries against the log_errors table. You can cross-reference host and component information, validate ingestion status across log_files, and export diagnostic results for further root-cause analysis.

Can I use SQL to cross-reference host and component data for DAQ diagnostics?

Yes, you can use SQL to cross-reference host and component data for DAQ diagnostics. The Skill supports joining log_files and log_errors tables, allowing you to filter by specific hosts or components to validate ingestion status and isolate failures.

How do I validate ingestion status across log_files and log_errors tables?

Validate ingestion status by running SELECT queries that join the log_files and log_errors tables. This approach lets you cross-reference file ingestion records with logged errors to identify missing data or processing failures within the DAQ pipeline.

Does the SQLite DAQ log query tool support exporting diagnostic results?

Yes, the SQLite DAQ log query tool supports exporting diagnostic results. You can use ordering and limiting clauses to refine your SELECT query output, and export the retrieved error data to support debugging and root-cause analysis workflows.

What are the limitations when querying DAQ logs with SQL?

Querying DAQ logs with SQL is limited to read-only SELECT statements. The Skill enforces this constraint to protect the SQLite database, meaning you cannot modify, insert, or delete log_files or log_errors records during diagnostic workflows.