Development
Skill
/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', 'set up alerts', 'cluster health check', or needs to set up Prometheus,
Claude Code
$ npx -y skills add qdrant/skills --skill qdrant-monitoring --agent claude-code
Codex
$ npx skills add qdrant/skills --skill qdrant-monitoring -a codex -y
Cursor
$ npx skills add qdrant/skills --skill qdrant-monitoring -a cursor -y
Gemini CLI
$ npx skills add qdrant/skills --skill qdrant-monitoring -a gemini-cli -y
GitHub Copilot
$ npx skills add qdrant/skills --skill qdrant-monitoring -a github-copilot -y
OpenCode
$ npx skills add qdrant/skills --skill qdrant-monitoring -a opencode -y
Windsurf
$ npx skills add qdrant/skills --skill qdrant-monitoring -a windsurf -y
SKILL.md
qdrant-monitoring.SKILL.mdname: qdrant-monitoring
description: "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', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis."
allowed-tools:
- Read
- Grep
- Glob
Qdrant 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` | | Want to send Qdrant metrics to Datadog | `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` | | Want to find which queries are slow (slow request log) | `debugging/SKILL.md` | | Need a per-collection memory or vector breakdown | `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](https://skills.qdrant.tech/md/documentation/ops-monitoring/monitoring/)
Read more
name: qdrant-monitoring description: "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', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis." allowed-tools: - Read - Grep - Glob
Qdrant 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` | | Want to send Qdrant metrics to Datadog | `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` | | Want to find which queries are slow (slow request log) | `debugging/SKILL.md` | | Need a per-collection memory or vector breakdown | `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](https://skills.qdrant.tech/md/documentation/ops-monitoring/monitoring/)
Stats
270
Stars
32
Forks
Active
Maintenance
Python
Language
Apache-2.0
License
Last commit
Created
Ships withqdrant
Agent skills for building with Qdrant vector search Skills encode deep Qdrant knowledge so coding agents can make the engineering decisions that determine whether vector search works well: quantization, sharding, tenant isolation, hybrid search, model
27033 skills
Stars on GitHub
Momentum
- stars in total
- 270
Other skills on qdrant.
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about qdrant-monitoring.
- Which coding agents can use qdrant-monitoring?
- qdrant-monitoring installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.