jdbc-metrics

Parse p6spy JDBC metrics logs into markdown reports with filtering and pagination.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/jonasalessi/playground-mcp-skills --skill jdbc-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jdbc-metrics
Source: https://github.com/jonasalessi/playground-mcp-skills/tree/main/.agents/skills/jdbc-metrics
Command: npx skills add https://github.com/jonasalessi/playground-mcp-skills --skill jdbc-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Parse p6spy JDBC metrics logs into readable markdown metrics.

Core Features & Use Cases

  • Parse and render SQL execution metrics from p6spy logs in markdown format.
  • Filter by minimum execution duration and paginate results for large logs.
  • Use case: quickly surface the slowest queries from a long log file for analysis.

Quick Start

Provide a p6spy log file path and optional filters, and run the script to obtain a markdown-formatted metrics report.

Frequently Asked Questions about jdbc-metrics

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

FAQPage Schema
How do I parse p6spy JDBC metrics logs into readable markdown?

To parse p6spy JDBC metrics logs into readable markdown, provide the log file path and run the script. It splits entries on the first three pipes to ensure correct parsing and outputs results newest-first.

Can I filter p6spy logs to show only slow SQL queries?

Yes, you can filter p6spy logs to show only slow SQL queries by applying the min_duration_ms parameter. This surfaces only the SQL execution metrics that exceed your specified duration threshold.

How do I handle large p6spy log files when analyzing JDBC metrics?

You can handle large p6spy log files when analyzing JDBC metrics by using offset and limit pagination controls. This allows you to process and render manageable chunks of the log data as markdown.

What happens to invalid lines when parsing JDBC metrics from p6spy logs?

Invalid lines are handled gracefully when parsing JDBC metrics from p6spy logs. The parser splits entries on the first three pipes and skips malformed data without failing the entire parsing operation.

What format do I need for parsing SQL execution metrics from p6spy logs?

Parsing SQL execution metrics requires p6spy log files in the specified pipe-delimited format. The parser operates on logs structured with fields separated by pipes to extract execution duration and query details.