Qdrant Monitoring

From the author

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.

— the description by Qdrant

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a navigational hub for Qdrant observability, directing users to specific documentation based on their operational needs. It covers the setup of monitoring stacks like Prometheus and Grafana, as well as diagnostic procedures for common production issues such as memory growth, slow requests, and optimizer performance.

What it does

Routes monitoring setup requests to relevant configuration guides.
Directs users to troubleshooting steps for production performance issues.
Identifies key metrics for tracking cluster health and resource utilization.
Provides guidance on integrating external monitoring tools like Datadog.
Helps diagnose specific symptoms like stuck optimizers or memory leaks.

When to use it

When configuring Prometheus, Grafana, or health checks for Qdrant.
When investigating performance bottlenecks or slow query requests.
When troubleshooting resource issues like unexpected memory growth.
When setting up alerting or log centralization for a production cluster.
When performing a general health check on a Qdrant deployment.

Advantages

Streamlines the process of finding specific operational documentation.
Connects symptoms directly to relevant diagnostic procedures.
Ensures users consult official metric references before making tuning changes.

Usage examples

“How do I set up Prometheus and Grafana for my Qdrant cluster?”: The agent will route you to the setup documentation for configuring your monitoring stack.
“My Qdrant memory usage is constantly growing, how do I debug this?”: The agent will direct you to the debugging guide specifically for memory and performance analysis.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/qdrant/qdrant-monitoring/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip qdrant-monitoring.zip -d .agents/skills

Documentation by Qdrant

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

Files

ATTRIBUTION.mdAdded by AutoGineer846 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md1.6 KiB

Requirements and compatibility

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.

Observability And Instrumentation
Addy Osmani· Community
A systematic approach to instrumenting production code with structured logs, metrics, and traces for effective system observability.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Spark Memory Thermal Ops
Seth Hobson· Community
Manage unified memory and thermal constraints for long-running machine learning jobs on NVIDIA DGX Spark.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository42.3k
Gke Alert Configuration
GoogleOfficial
Configure GKE alerting policies in Terraform using PromQL and Google Cloud Managed Service for Prometheus.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0Low riskHas scriptsGitHub stars of the source repository23.2k
Application Performance Observability Engineer
Seth Hobson· Community
Expert observability engineer for designing production-grade monitoring, logging, tracing, and reliability systems.
Cloud and DevOpsClaude Code
MITGitHub stars of the source repository42.3k
Distributed Debugging Devops Troubleshooter
Seth Hobson· Community
An expert DevOps troubleshooter for incident response, system reliability, and complex distributed system debugging.
Cloud and DevOpsClaude Code
MITGitHub stars of the source repository42.3k
Distributed Tracing
Seth Hobson· Community
Implement distributed tracing using Jaeger and Tempo to monitor request flows and performance across microservices.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k