Routes Qdrant monitoring questions to setup or debugging guidance for metrics, alerts, and health checks.
- What it does
- This skill acts as a router for Qdrant monitoring and observability questions. It matches a user's symptom or request against a table and directs the agent to read either a setup guide or a debugging guide. Topics covered include Prometheus and Grafana setup, metric selection, alerting, log centralization, Hybrid Cloud metrics, optimizer issues, memory growth, slow requests, and cluster health. It produces guidance rather than files or scripts.
- When to use it
- Use when someone asks how to monitor Qdrant, which metrics to track, whether a cluster is healthy, or how to set up Prometheus, Grafana, health checks, or alerts. Also use when debugging production Qdrant issues such as a stuck optimizer, growing memory, or slow requests that require metric analysis.
- Requirements
- Instructions only; no scripts are included. The agent needs file-reading capability to open the referenced setup and debugging files. The document references external monitoring documentation, so network access may be needed to view it.
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.
Qdrant monitoring tracks performance and health, and catches issues before they become outages. See the metric reference before tuning anything:
Monitoring docs