Index of every page on this site: llms.txt
All skills
github avatar

/debugging

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.

  • 1 file
  • 3.4 KB
  • Updated 7 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/github/awesome-copilot/debugging

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈80 tokens for metadata: the name and description. ≈784 when used: this file.

Description uses 4.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈340 characters, or 4.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

How to Debug Qdrant with Metrics

First check optimizer status. Most production issues trace back to active optimizations competing for resources. If optimizer is clean, check memory, then request metrics.

Optimizer Stuck or Too Slow

Use when: optimizer running for hours, not finishing, or showing errors.

  • Use /collections/{collection_name}/optimizations endpoint (v1.17+) to check status Optimization monitoring
  • Query with optional detail flags: ?with=queued,completed,idle_segments
  • Returns: queued optimizations count, active optimizer type, involved segments, progress tracking
  • Web UI has an Optimizations tab with timeline view and per-task duration metrics Web UI
  • If optimizer_status shows an error in collection info, check logs for disk full or corrupted segments
  • Large merges and HNSW rebuilds legitimately take hours on big datasets. Check progress before assuming it's stuck.

Memory Seems Too High

Use when: memory exceeds expectations, node crashes with OOM, or memory keeps growing.

  • Process memory metrics available via /metrics (RSS, allocated bytes, page faults)
  • Qdrant uses two types of RAM: resident memory (data structures, quantized vectors) and OS page cache (cached disk reads). Page cache filling available RAM is normal. Memory article
  • If resident memory (RSSAnon) exceeds 80% of total RAM, investigate
  • Check /telemetry for per-collection breakdown of point counts and vector configurations
  • Estimate expected memory: num_vectors * dimensions * 4 bytes * 1.5 for vectors, plus payload and index overhead Capacity planning
  • Common causes of unexpected growth: quantized vectors with always_ram=true, too many payload indexes, large max_segment_size during optimization

Queries Are Slow

Use when: queries slower than expected and you need to identify the cause.

  • Track rest_responses_avg_duration_seconds and rest_responses_max_duration_seconds per endpoint
  • Use histogram metric rest_responses_duration_seconds (v1.8+) for percentile analysis in Grafana
  • Equivalent gRPC metrics with grpc_responses_ prefix
  • Check optimizer status first. Active optimizations compete for CPU and I/O, degrading search latency.
  • Check segment count via collection info. Too many unmerged segments after bulk upload causes slower search.
  • Compare filtered vs unfiltered query times. Large gap means missing payload index. Payload index

What NOT to Do

  • Ignore optimizer status when debugging slow queries (most common root cause)
  • Assume memory leak when page cache fills RAM (normal OS behavior)
  • Make config changes while optimizer is running (causes cascading re-optimizations)
  • Blame Qdrant before checking if bulk upload just finished (unmerged segments)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago

README badge

README badge for github/awesome-copilot/debugging

Diagnoses Qdrant production issues by checking optimizer status, memory consumption, and request latency metrics. Targets problems like stuck optimizations, OOM crashes, slow queries, and unexplained latency spikes using Qdrant's `/metrics` and `/optimizations` endpoints.

Generated from the current SKILL.md.

Does this skill work with Qdrant Cloud or only self-hosted?
The skill focuses on self-hosted Qdrant where you have direct access to metrics endpoints and logs. Qdrant Cloud exposes some metrics but the debugging workflow assumes access to `/metrics`, `/telemetry`, and collection optimization endpoints.
What Qdrant version do I need?
The skill targets v1.8+ for histogram metrics and v1.17+ for the `/collections/{collection_name}/optimizations` endpoint. Older versions have limited observability for the optimizer debugging workflows described.
Can this help with connection timeouts or network errors?
No. The skill addresses production performance issues (slow queries, high memory, stuck optimizations) and does not cover network connectivity, authentication, or gRPC/REST client errors.
Do I need to install monitoring tools like Prometheus or Grafana?
The skill assumes you can query Qdrant's built-in `/metrics` and `/telemetry` endpoints directly. Grafana is mentioned for percentile analysis but not required; you can interpret metrics without it.

Generated from the current SKILL.md. These answers refresh after source changes.