hologres-slow-query-analysis

Analyze slow Hologres queries from hologres.hg_query_log and diagnose root causes.

17|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aliyun/hologres-ai-plugins --skill hologres-slow-query-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hologres-slow-query-analysis
Source: https://github.com/aliyun/hologres-ai-plugins/tree/main/agent-skills/skills/hologres-slow-query-analysis
Command: npx skills add https://github.com/aliyun/hologres-ai-plugins --skill hologres-slow-query-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes slow and failed Hologres queries by inspecting the hologres.hg_query_log data to identify bottlenecks, root causes, and optimization opportunities.

Core Features & Use Cases

  • Top slow query identification, per-digest aggregation, and per-query detail views for targeted optimization.
  • Instance-wide slow query analytics: compute total counts, durations, and distribution across engines (HQE, PQE, SDK/FixedQE, PG).
  • Per-query deep-dive: inspect plan, resources, reads/writes, and execution details for a given query_id; generate actionable recommendations.
  • Real-world use case: diagnose a spike in slow queries during peak hours and propose schema/plan improvements to restore performance.

Quick Start

Run a concise, end-to-end diagnostic for a defined time window using hologres.hg_query_log to surface bottlenecks and recommended optimizations.

Frequently Asked Questions about hologres-slow-query-analysis

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

FAQPage Schema
How do I diagnose slow queries in Hologres using query logs?

Diagnose slow queries in Hologres by inspecting the hologres.hg_query_log within a specified time window to identify bottlenecks, aggregate top slow queries by digest, and surface root causes across engines. This yields actionable optimization recommendations and detailed execution plans.

Why does my Hologres query execution fail or experience latency spikes across different engines?

Hologres query latency spikes or failures stem from execution bottlenecks across specific engines like HQE, PQE, SDK/FixedQE, or PG. Analyzing the hologres.hg_query_log surfaces these root causes, highlighting resource reads, writes, and plan details for targeted performance tuning.

Can I analyze instance-wide Hologres slow query distributions for peak hours?

Yes, you can analyze instance-wide slow query analytics by computing total counts, durations, and distributions across Hologres engines for a defined time window. This identifies peak hour spikes and aggregates query digests to propose schema or plan improvements.

How do I get actionable optimization recommendations for a specific Hologres query_id?

Perform a per-query deep-dive on a specific Hologres query_id by inspecting its execution plan, resources, reads, writes, and engine details from the query log. This generates actionable optimization recommendations tailored to that exact query's execution profile.

Does Hologres query log analysis respect database privileges and filter inaccessible results?

Yes, Hologres query log analysis respects safety and privileges by filtering diagnostic results based on available access and documented error codes. This ensures structured instance-wide and per-query diagnostics only surface data you are authorized to inspect.