# Qdrant monitoring setup

> Qdrant monitoring setup is an open-source agent skill for knowledge and memory. Guides setting up Prometheus scraping, health probes, alerting and logs for Qdrant. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/github/awesome-copilot/tree/main/skills/qdrant-monitoring/setup
- **Repository:** https://github.com/github/awesome-copilot
- **GitHub stars:** 41,333
- **License:** MIT
- **Skill name:** qdrant-monitoring-setup
- **Collection:** https://github.com/github/awesome-copilot
- **Categories:** [knowledge and memory](https://ai-powered.com/categories/knowledge-and-memory), [web search and scraping](https://ai-powered.com/categories/web-search-and-scraping), [databases](https://ai-powered.com/categories/databases), [developer tools](https://ai-powered.com/categories/developer-tools), [cloud and infrastructure](https://ai-powered.com/categories/cloud-and-infrastructure)
- **Listing updated:** 2026-11-18

## About

This skill walks an agent through configuring observability for a Qdrant deployment, in a fixed order: get Prometheus scraping working first, then add health probes, then alerting. It covers node metrics at the /metrics endpoint, the Qdrant Cloud-only cluster metrics endpoint, and renaming the metrics prefix through config or an environment variable.

For Hybrid Cloud deployments the skill points out that scraping Qdrant nodes alone is not enough, since the cluster-exporter and operator pods also need to be scraped. It references existing tutorials and Grafana dashboard repositories, and notes that Hybrid Cloud ships with about eleven pre-configured Prometheus alerts. It suggests a minimum alert set covering optimizer errors, nodes not ready, replication factor shortfalls and disk usage above 80%, and advises against alerting on page cache usage.

For logging, the skill covers switching the logger to JSON format, aggregating with FluentD or OpenSearch, and handling audit logs from v1.17 onward, which are written to a local path rather than stdout. It expects a Kubernetes or self-hosted Qdrant setup and works with Prometheus, Grafana and Alertmanager; no scripts are included.

## When your agent uses it

> Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization. Use when someone asks 'how to set up monitoring', 'Prometheus config', 'Grafana dashboard', 'health check endpoints', 'how to scrape Hybrid Cloud', 'what alerts to set', 'how to centralize logs', or 'audit logging'.

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Instructions only, no scripts](https://github.com/github/awesome-copilot/tree/HEAD/skills/qdrant-monitoring/setup)
- [License: MIT](https://github.com/github/awesome-copilot/tree/HEAD/skills/qdrant-monitoring/setup)

## Features

- **Prometheus metrics collection:** Covers scraping node metrics from the /metrics endpoint and customizing the metrics prefix.
- **Hybrid Cloud scraping:** Explains which cluster-exporter and operator pods to scrape alongside Qdrant nodes.
- **Kubernetes health probes:** Describes using the healthz, livez and readyz endpoints for status and liveness checks.
- **Alerting guidance:** Lists a minimum set of production alerts and how to route them with AlertmanagerConfig.
- **Structured log setup:** Shows how to switch logs to JSON format for analysis and aggregation.
- **Audit log forwarding:** Explains moving audit logs from the filesystem to stdout with a sidecar container.

## Good for

- Set up Prometheus scraping for a self-hosted Qdrant cluster
- Configure Kubernetes liveness and readiness probes for Qdrant
- Scrape a Qdrant Hybrid Cloud deployment including operator metrics
- Decide which alerts to create before taking Qdrant to production
- Centralize Qdrant logs with FluentD or OpenSearch
- Forward Qdrant audit logs to stdout for DaemonSet collection

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/qdrant-monitoring-setup` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/qdrant-monitoring-setup &&
cp -R "$tmp/skills/qdrant-monitoring/setup" ~/.claude/skills/qdrant-monitoring-setup &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/qdrant-monitoring-setup` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/qdrant-monitoring-setup` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/qdrant-monitoring-setup &&
cp -R "$tmp/skills/qdrant-monitoring/setup" ~/.agents/skills/qdrant-monitoring-setup &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/qdrant-monitoring-setup` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/qdrant-monitoring-setup` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/qdrant-monitoring-setup &&
cp -R "$tmp/skills/qdrant-monitoring/setup" ~/.cursor/skills/qdrant-monitoring-setup &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/qdrant-monitoring-setup` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/github/awesome-copilot.git --path skills/qdrant-monitoring/setup
```

Or copy the folder to `~/.gemini/skills/qdrant-monitoring-setup` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/qdrant-monitoring-setup`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/qdrant-monitoring-setup &&
cp -R "$tmp/skills/qdrant-monitoring/setup" ~/.copilot/skills/qdrant-monitoring-setup &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/qdrant-monitoring-setup` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/github/awesome-copilot.git
```

Then copy `awesome-copilot/skills/qdrant-monitoring/setup` into your agent's skills folder as `qdrant-monitoring-setup`. Agents that support SKILL.md read one folder per skill.

## FAQ

### Does this skill run any scripts or change my cluster?

No scripts are included. It guides configuration steps and references existing tutorials and repositories.

### Is the /sys_metrics endpoint available on self-hosted Qdrant?

No. The skill states that cluster metrics at /sys_metrics are only available on Qdrant Cloud.

### Which alerts does it recommend at minimum?

It recommends alerting on optimizer errors, node not ready, replication factor below target, and disk usage above 80%.

### Where do Qdrant audit logs go in v1.17 and later?

They are written to /qdrant/storage/audit/ on the local filesystem rather than stdout, so the skill suggests a sidecar to tail them.

### How do I install Qdrant monitoring setup in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/qdrant-monitoring-setup to use it in all your projects, or to .claude/skills/qdrant-monitoring-setup in one project.

### Does Qdrant monitoring setup run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Qdrant monitoring setup?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

### What are the best alternatives to Qdrant monitoring setup?

The closest alternatives to Qdrant monitoring setup are Qdrant monitoring, Qdrant monitoring debugging, Qdrant scaling data volume, Qdrant scaling query volume and Qdrant vertical scaling.

## Where this comes from

- Description: from the skill's own SKILL.md.

## Alternatives

- [Qdrant monitoring](https://ai-powered.com/skills/qdrant-monitoring): Qdrant monitoring is an open-source agent skill for knowledge and memory.
- [Qdrant monitoring debugging](https://ai-powered.com/skills/qdrant-monitoring-debugging): Qdrant monitoring debugging is an open-source agent skill for knowledge and memory.
- [Qdrant scaling data volume](https://ai-powered.com/skills/qdrant-scaling-data-volume): Qdrant scaling data volume is an open-source agent skill for knowledge and memory.
- [Qdrant scaling query volume](https://ai-powered.com/skills/qdrant-scaling-query-volume): Qdrant scaling query volume is an open-source agent skill for knowledge and memory.
- [Qdrant vertical scaling](https://ai-powered.com/skills/qdrant-vertical-scaling): Qdrant vertical scaling is an open-source agent skill for knowledge and memory.
- [Qdrant deployment options](https://ai-powered.com/skills/qdrant-deployment-options): Qdrant deployment options is an open-source agent skill for knowledge and memory.
- [Qdrant scaling qps](https://ai-powered.com/skills/qdrant-scaling-qps): Qdrant scaling qps is an open-source agent skill for knowledge and memory.
- [Qdrant horizontal scaling](https://ai-powered.com/skills/qdrant-horizontal-scaling): Qdrant horizontal scaling is an open-source agent skill for knowledge and memory.

---
Source: https://ai-powered.com/skills/qdrant-monitoring-setup
