Catalog
github/qdrant-monitoring

github

qdrant-monitoring

Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', or needs to set up Prometheus, Grafana, or health checks. Also use when debugging production issues that require metric analysis.

global
Allowed Tools
ReadGrepGlob
New~254
v1.0Saved Jul 12, 2026

Qdrant Monitoring

Qdrant monitoring allows tracking performance and health of your deployment, and identifying issues before they become outages. First determine whether you need to set up monitoring or diagnose an active issue.

Monitoring Setup

Prometheus scraping, health probes, Hybrid Cloud specifics, alerting, and log centralization. Monitoring Setup

Debugging with Metrics

Optimizer stuck, memory growth, slow requests. Using metrics to diagnose active production issues. Debugging with Metrics

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

52/100

Grade

C

Adequate

Safety

88

Quality

45

Clarity

58

Completeness

35

Summary

This skill guides users through Qdrant monitoring and observability setup, including Prometheus/Grafana configuration, health checks, and metric-driven debugging. It delegates to two sub-skills (setup and debugging) and provides read-only guidance on tracking performance, identifying bottlenecks, and diagnosing production issues.

Detected Capabilities

read operationsdocumentation referencemetric analysis guidancehealth check configurationalert setup

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

qdrant monitoring setupprometheus grafanaqdrant health checksoptimizer stuck issuememory growth diagnosisslow request debuggingqdrant metrics

Risk Signals

INFO

References external domain (search.qdrant.tech) for documentation

SKILL.md frontmatter description and content
WARNING

Sub-skill delegation (setup/SKILL.md, debugging/SKILL.md) — referenced files not provided in manifest

SKILL.md content

Referenced Domains

External domains referenced in skill content, detected by static analysis.

search.qdrant.tech

Use Cases

  • Set up Prometheus scraping and Grafana dashboards for Qdrant
  • Monitor Qdrant health probes and configure alerting rules
  • Debug slow requests using query latency metrics
  • Investigate optimizer stuck issues via segment metrics
  • Diagnose memory growth and analyze resource utilization
  • Troubleshoot production performance degradation with metric analysis

Quality Notes

  • Skill appropriately uses read-only allowed-tools (Read, Grep, Glob) with no file writes or destructive operations
  • Clear trigger scenarios provided in description (optimizer stuck, memory growth, slow requests, health checks)
  • Scope is well-bounded to monitoring and observability; does not attempt infrastructure provisioning
  • Critical issue: Referenced sub-skills (setup/SKILL.md and debugging/SKILL.md) are not provided in the manifest, making the skill incomplete and untestable
  • Minimal inline guidance — skill primarily delegates to external documentation and sub-skills rather than providing actionable steps
  • No examples, no edge case coverage (e.g., incomplete metrics, monitoring unavailable), no troubleshooting table
Model: claude-haiku-4-5-20251001Analyzed: Jul 12, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/qdrant-monitoring in your dev environment

Command Palette

Search for a command to run...