New to Claude Skills? Learn how to install them →

github on GitHub

Qdrant Monitoring Setup

OfficialFree

Streamline your Qdrant monitoring with Prometheus and Grafana.

by github37.7k stars on github/awesome-copilot
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Qdrant Monitoring Setup does

The Qdrant Monitoring Setup skill provides a comprehensive guide for implementing monitoring for Qdrant deployments using Prometheus and Grafana. This skill is essential for developers and system administrators who need to ensure their Qdrant instances are properly monitored before going into production. It covers the necessary steps for setting up Prometheus scraping, health probes, alerting, and log centralization, ensuring that users have a clear path to effective monitoring.

The setup begins with configuring Prometheus metrics collection, detailing how to access node and cluster metrics through specific endpoints. For those utilizing Qdrant in a Hybrid Cloud environment, the skill emphasizes the importance of scraping not just Qdrant nodes but also the cluster-exporter and operator pods for complete visibility. It also includes links to official documentation and example setups, making it easier for users to follow along.

In addition to metrics, the skill outlines how to implement liveness and readiness probes within Kubernetes, which are critical for maintaining application health. It also provides guidance on setting up alerting mechanisms, including pre-configured alerts for common issues and how to route alerts to various notification services. Finally, the skill addresses log centralization and audit logging, which are crucial for enterprise compliance and structured analysis of logs.

Overall, this skill is targeted at those who are deploying Qdrant, particularly in production or Hybrid Cloud environments, and require a robust monitoring setup to maintain performance and reliability.

When to use it

Use this skill when you need to set up monitoring for Qdrant, especially in production or Hybrid Cloud scenarios.

When not to use it

This skill may not be suitable if you are not using Qdrant or if you require monitoring for a different database system.

What you can build with it

Setting Up Monitoring for Production

Use this skill to establish a monitoring setup for Qdrant before deploying to production, ensuring all metrics are tracked.

Configuring Hybrid Cloud Metrics

Leverage this skill to configure Prometheus scraping for both Qdrant nodes and Kubernetes components in a Hybrid Cloud setup.

Implementing Alerting Mechanisms

Follow this skill to set up alerts for critical metrics, enabling proactive monitoring and response to issues.

How to install Qdrant Monitoring Setup

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/setup --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by github

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 /metrics endpoint Monitoring docs
  • Cluster metrics at /sys_metrics (Qdrant Cloud only)
  • Prefix customization via service.metrics_prefix config or QDRANT__SERVICE__METRICS_PREFIX env var
  • Example 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.

Liveness and Readiness Probes

Use when: configuring Kubernetes health checks.

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.format to json in config Configuration
  • Use 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_metrics on 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)

Frequently asked questions about Qdrant Monitoring Setup

Similar skills