About qdrant-monitoring
A routing skill for monitoring Qdrant deployments. It directs agents to setup or debugging guidance based on needs such as metrics, alerting, memory growth, slow requests, and health checks.
Key features
- 01Monitoring topic routing
- 02Prometheus and Grafana setup guidance
- 03Metrics and alerting guidance
- 04Production issue debugging
- 05Health and performance checks
Use cases
- 01Choosing metrics and configuring monitoring
- 02Investigating optimizer stalls or growing memory use
- 03Checking Qdrant health and diagnosing slow requests
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/qdrant-monitoringin Claude Code to confirm it loaded.
Details
From the project READMEQdrant Monitoring
Route first, then answer. Match the user's symptom in the table, Read that file, and answer from it.
Do not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.
| The user says | Read |
|---|---|
| Want to set up Prometheus, Grafana, or health checks | setup/SKILL.md |
| Need to know which metrics to track | setup/SKILL.md |
| Setting up alerting, log centralization, or Hybrid Cloud metrics | setup/SKILL.md |
| Optimizer stuck or running forever | debugging/SKILL.md |
| Memory keeps growing in production | debugging/SKILL.md |
| Requests are slow and I need to find out why | debugging/SKILL.md |
| Is Qdrant healthy right now | debugging/SKILL.md |
Qdrant monitoring tracks performance and health, and catches issues before they become outages. See the metric reference before tuning anything: Monitoring docs
Comments
Markdown supported