sql-debugging

Diagnose Oxla cluster issues via system tables, Prometheus metrics, and runtime log levels.

6|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/redpanda-data/skills --skill sql-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-debugging
Source: https://github.com/redpanda-data/skills/tree/main/skills/sql-debugging
Command: npx skills add https://github.com/redpanda-data/skills --skill sql-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and troubleshoot Oxla debugging and observability challenges across system tables, metrics, and runtime configuration, enabling faster root-cause analysis and remediation.

Core Features & Use Cases

  • Inspect cluster health via system.nodes, system.queries, system.execs, and storage_connections.
  • Query Prometheus metrics on port 8080 to pinpoint memory pressure, admission bottlenecks, and query latency.
  • Adjust log levels at runtime via the admin gRPC API to gain deeper visibility during investigations.
  • Follow troubleshooting playbooks to identify root causes and apply remedial steps for common scenarios.

Quick Start

Connect to Oxla with psql, run baseline queries against system tables (system.nodes, system.queries, system.execs, system.catalogs, storage_connections), and inspect Prometheus metrics on port 8080 to correlate symptoms with cluster state.

Frequently Asked Questions about sql-debugging

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

FAQPage Schema
How do I troubleshoot slow queries and memory pressure in Oxla?

Troubleshoot slow queries and memory pressure in Oxla by querying system tables like system.queries and system.execs, then correlating symptoms with Prometheus metrics on port 8080 to pinpoint admission bottlenecks and query latency.

What system tables are available for Oxla cluster observability and debugging?

Oxla cluster observability leverages system tables including system.nodes, system.queries, system.execs, system.catalogs, and storage_connections to inspect cluster health, node states, and query execution details.

How do I adjust Oxla log levels at runtime during an investigation?

Adjust Oxla log levels at runtime by using the admin gRPC API, allowing you to gain deeper visibility and control over logging output during active troubleshooting investigations.

How can I diagnose ingestion stalls and node health issues across my Oxla cluster?

Diagnose Oxla ingestion stalls and node health issues by inspecting cluster state via system.nodes and storage_connections, and querying Prometheus metrics to identify resource constraints or admission bottlenecks.

Do I need Prometheus to monitor Oxla query latency and admission bottlenecks?

Prometheus metrics exposed on port 8080 are used to monitor Oxla query latency, memory pressure, and admission bottlenecks, providing quantitative data to correlate with system table observations.

What's the best way to start debugging an Oxla cluster for root-cause analysis?

Start debugging an Oxla cluster by connecting with psql, running baseline queries against system tables like system.nodes and system.queries, and inspecting Prometheus metrics on port 8080 to correlate symptoms.