Qdrant Monitoring Setup
GitHubOfficialFirst committed by anush008Distributed by GitHub
- Skill
- Guidelines
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides structured guidance on setting up observability for Qdrant, covering metric collection, Kubernetes health probes, alerting strategies, and log management. It details how to configure Prometheus scraping for both self-hosted and Hybrid Cloud environments, how to implement liveness and readiness checks, and how to manage audit logs for enterprise requirements.
What it does
- Explains Prometheus metric endpoint configuration for Qdrant nodes.
- Details health check endpoints for Kubernetes liveness and readiness probes.
- Provides guidance on scraping metrics in Hybrid Cloud environments.
- Outlines essential alerting criteria for cluster health.
- Describes how to enable structured JSON logging and centralize audit logs.
When to use it
- When configuring monitoring for a new Qdrant deployment.
- When setting up Kubernetes health probes for Qdrant pods.
- When implementing alerting rules for cluster operations.
- When establishing log aggregation and audit trails for compliance.
Advantages
- Centralizes best practices for Qdrant observability.
- Clarifies differences between self-hosted and Hybrid Cloud monitoring requirements.
- Provides specific guidance on handling audit logs via sidecar containers.
- Helps avoid common pitfalls like misconfiguring alerts for page cache memory.
Usage examples
- “How do I set up Prometheus scraping for Qdrant?”
- The agent provides instructions on using the /metrics endpoint and configuring the service metrics prefix.
- “What are the recommended health check endpoints for Qdrant?”
- The agent lists the /healthz, /livez, and /readyz endpoints for Kubernetes probe configuration.
- “How do I centralize audit logs for Qdrant?”
- The agent explains how to enable JSON logging and use a sidecar container to tail audit logs from the storage directory.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/qdrant-monitoring-setup/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip qdrant-monitoring-setup.zip -d .agents/skills
Documentation by anush008
How to Set Up Qdrant Monitoring
Get Prometheus scraping working first, then health probes, then alerting. Do not skip monitoring setup before going to production.
Prometheus Metrics
Use when: setting up metric collection for the first time or adding a new deployment.
Node metrics at
/metricsendpoint Monitoring docsCluster metrics at
/sys_metrics(Qdrant Cloud only)Prefix customization via
service.metrics_prefixconfig orQDRANT__SERVICE__METRICS_PREFIXenv varExample self-hosted setup with Prometheus + Grafana prometheus-monitoring repo
Hybrid Cloud Scraping
Use when: running Qdrant Hybrid Cloud and need cluster-level visibility.
Do not just scrape Qdrant nodes. In Hybrid Cloud, you manage the Kubernetes data plane. You must also scrape the cluster-exporter and operator pods for full cluster visibility and operator state.
Hybrid Cloud Prometheus setup tutorial Hybrid Cloud Prometheus
Official Grafana dashboards Grafana dashboard repo
Liveness and Readiness Probes
Use when: configuring Kubernetes health checks.
Use
/healthz,/livez,/readyzfor basic status, liveness, and readiness Kubernetes health endpoints
Alerting
Use when: setting up alerts for production or Hybrid Cloud deployments.
Hybrid Cloud provides ~11 pre-configured Prometheus alerts out of the box Cloud cluster monitoring
Use AlertmanagerConfig to route alerts to Slack, PagerDuty, or other targets based on labels
At minimum, alert on: optimizer errors, node not ready, replication factor below target, disk usage >80%
Log Centralization and Audit Logging
Use when: enterprise compliance requires centralized logs or audit trails.
Enable JSON log format for structured analysis: set
logger.formattojsonin config ConfigurationUse FluentD/OpenSearch for log aggregation
Audit logs (v1.17+) write to local filesystem (
/qdrant/storage/audit/), not stdout. Mount a Persistent Volume and deploy a sidecar container to tail these files to stdout so DaemonSets can pick them up. Audit logging
What NOT to Do
Scrape
/sys_metricson self-hosted (only available on Qdrant Cloud)Scrape only Qdrant nodes in Hybrid Cloud (miss cluster-exporter and operator metrics)
Skip monitoring setup before going to production (you will regret it)
Alert on page cache memory usage (it's supposed to fill available RAM, normal OS behavior)
Files
- ATTRIBUTION.mdAdded by AutoGineer879 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md3.3 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: Needs Node.js
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/setup · 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-setup.zip