agent-log-debugging

Query Breeze agent diagnostic logs from Postgres to identify connectivity and error issues.

73|23|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/LanternOps/breeze --skill agent-log-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-log-debugging
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/agent-log-debugging
Command: npx skills add https://github.com/LanternOps/breeze --skill agent-log-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and diagnose Breeze agent issues by querying diagnostic logs directly from the Postgres database.

Core Features & Use Cases

  • Directly query agent_logs and related tables to surface recent errors, warnings, and connectivity issues.
  • Provide quick references for common scenarios such as agent not connecting, heartbeat failures, and log shipping status.
  • Offer commands and workflows to enable verbose debugging (set_log_level) and to inspect device-agent mappings and commands.

Quick Start

Run the example queries to inspect agent connectivity and recent errors in the breeze database.

Frequently Asked Questions about agent-log-debugging

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

FAQPage Schema
How do I query Breeze agent logs from a Postgres database to diagnose connectivity issues?

To debug Breeze agent logs, query the agent_logs table in the Postgres database to surface recent errors, warnings, and device-agent connectivity issues across your Dockerized deployment.

What is the best way to check heartbeat failures for Dockerized Breeze agents?

Checking heartbeat failures involves running example SQL queries against the breeze database to inspect agent connectivity, view recent log entries, and interpret device-agent mapping status.

Do I need direct Postgres access to debug Breeze agent diagnostic logs?

Yes, debugging Breeze agent logs requires direct access to the Breeze Postgres instance to execute SQL references that adjust log levels, view logs, and inspect agent commands.

How can I enable verbose debugging for a Breeze agent that is not connecting?

You can enable verbose debugging by using the provided set_log_level commands and workflows within the database to inspect detailed diagnostic logs and resolve agent connectivity failures.

Why is my Breeze agent not shipping logs correctly in a Docker deployment?

Log shipping status issues can be diagnosed by querying the diagnostic logs directly from the Postgres database to surface recent errors, inspect device-agent mappings, and review agent commands.