Qdrant Monitoring
GitHubOfficialFirst committed by anush008Distributed by GitHub
- Skill
- Tool integration
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The qdrant-monitoring skill provides a structured approach to maintaining the health and performance of Qdrant vector database deployments. It serves as a central reference for configuring monitoring stacks, including Prometheus and Grafana, and offers diagnostic pathways for common production challenges such as memory growth, slow request latency, and optimizer bottlenecks.
What it does
- Explains how to configure Prometheus scraping and health probes for Qdrant.
- Identifies key performance metrics to track for cluster health.
- Provides guidance on setting up log centralization and alerting.
- Offers diagnostic steps for troubleshooting stuck optimizers.
- Helps analyze memory consumption patterns and request latency issues.
When to use it
- When setting up initial observability for a new Qdrant deployment.
- When investigating production performance degradation.
- When you need to determine if a Qdrant instance is healthy.
- When troubleshooting specific issues like high memory usage or slow queries.
Advantages
- Centralizes best practices for Qdrant-specific observability.
- Reduces downtime by enabling proactive metric tracking.
- Provides actionable diagnostic paths for complex production issues.
Usage examples
- “How do I monitor my Qdrant instance?”
- The agent provides a guide on setting up Prometheus scraping and configuring health probes to track cluster performance.
- “Why is my Qdrant memory usage growing?”
- The agent directs you to specific metrics and diagnostic steps to identify potential memory leaks or inefficient resource usage.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/qdrant-monitoring/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip qdrant-monitoring.zip -d .agents/skills
Documentation by anush008
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.
Understand available metrics Monitoring docs
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
Files
- ATTRIBUTION.mdAdded by AutoGineer867 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.1 KiB
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- First committed by
anush008
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/qdrant-monitoring · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- anush008
AutoGineer is not affiliated with or endorsed by anush008 or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download qdrant-monitoring.zip