Official agent skill

Qdrant Monitoring Setup

Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Qdrant Monitoring Setup

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qdrant-monitoring/setup .claude/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .claude/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qdrant-monitoring/setup .agents/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .agents/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qdrant-monitoring/setup .cursor/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .cursor/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/qdrant/skills.git --path skills/qdrant-monitoring/setup

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qdrant-monitoring/setup .gemini/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .gemini/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qdrant-monitoring/setup .github/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .github/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add qdrant/skills --skill qdrant-monitoring-setup -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install qdrant/skills qdrant-monitoring-setup --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qdrant/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qdrant-monitoring/setup .opencode/skills/qdrant-monitoring-setup && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "qdrant-monitoring-setup" agent skill from https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup into .opencode/skills/qdrant-monitoring-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qdrant-monitoring-setup", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: qdrant-monitoring-setup
GitHub stars: 254
Used in: 2 other repos
Token cost: ~874 tokens
SKILL.md length: 341 words
Files: 1
Skills in repo: 33
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization.

Someone asks how to set up monitoring
SKILL.md covers Prometheus Metrics, Hybrid Cloud Scraping, Liveness and Readiness Probes and Alerting, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Prometheus config

What it does

Qdrant Monitoring Setup is an agent skill from qdrant/skills, published by the product's own GitHub organization. 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'.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Vector databases, Monitoring and alerting and Web scraping. It works with Qdrant, Prometheus, Grafana and Kubernetes. The repository describes itself as: Agent skills for Qdrant vector search: scaling, performance optimization, search quality, monitoring, deployment, model migration, version upgrades, and SDK usage across Python…. The licence is Apache-2.0.

When your agent uses it

Someone asks how to set up monitoring
Prometheus config
Grafana dashboard
Health check endpoints

Example prompts

“how to set up monitoring”
“Prometheus config”
“Grafana dashboard”
“/qdrant-monitoring-setup”

What it can do on your machine

Read from SKILL.md and the folder at commit 57658ea. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- skills.qdrant.tech
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qdrant Monitoring Setup loads about 874 tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 341 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~874

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qdrant/skills at commit 57658ea, republished under its Apache-2.0 licence (© qdrant). 341 words, ~874 tokens.

Download SKILL.mdSave it as .claude/skills/qdrant-monitoring-setup/SKILL.md (or your agent's skills folder).

name: qdrant-monitoring-setup
description: 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'.

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.

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, /readyz for basic status, liveness, and readiness Kubernetes health endpoints

Alerting

Use when: setting up alerts for production or Hybrid Cloud deployments.

Qdrant Cloud provides pre-configured email alerts for 11 cluster issues. Use scraped metrics when you need custom alerts or routing to other targets. See 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)

Files

Just SKILL.md in skills/qdrant-monitoring/setup of qdrant/skills.

Open the folder on GitHubat commit 57658ea

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in qdrant/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Qdrant Monitoring Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qdrant Monitoring Setup compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Qdrant Monitoring Setup this skillqdrant/skills	254	2 repos	~874	Automated safety check: Pass	Apache-2.0	today
Alloygrafana/skills	281	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Qdrant Monitoringgithub/awesome-copilot	40k	1 repos	~276	Automated safety check: Pass	MIT	today
Prometheus GrafanaBagelHole/DevOps-Security-Agent-Skills	1.1k	—	~2.5k	Automated safety check: Pass	MIT	4 mo ago
Grafana Dashboardpando85/kaniop	131	—	~987	Automated safety check: Pass	AGPL-3.0	today
Prometheus Grafanasickn33/agentic-awesome-skills	47k	1 repos	~2.7k	Automated safety check: Pass	MIT	today

Similar skills

Alloy
grafana/skills
Official
Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…
281 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check passed
Qdrant Monitoring
github/awesome-copilot
Official
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
40k GitHub starsUsed in 1 repo~276 tokens
DevOps & CloudAuto-check passed
Prometheus Grafana
BagelHole/DevOps-Security-Agent-Skills
Set up metrics collection and visualization with Prometheus and Grafana.
1.1k GitHub stars~2.5k tokensUpdated 4 mo ago
DevOps & CloudAuto-check passed
Grafana Dashboard
pando85/kaniop
Improve and validate the Kaniop Grafana dashboard against repository metrics and the grigri live cluster.
131 GitHub stars~987 tokensUpdated today
DevOps & CloudAuto-check passed
Prometheus Grafana
sickn33/agentic-awesome-skills
Set up metrics collection and visualization with Prometheus and Grafana.
47k GitHub starsUsed in 1 repo~2.7k tokens
DevOps & CloudAuto-check passed
Beyla
grafana/skills
Official
Auto-instrument an application's HTTP / gRPC / DB traffic with Grafana Beyla eBPF — no code changes, no SDK, no restart.
281 GitHub stars~1.1k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Qdrant Monitoring Setup

What does Qdrant Monitoring Setup do?

Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization. Qdrant Monitoring Setup is an agent skill from qdrant/skills, published by the product's own GitHub organization. Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization.

When should I use Qdrant Monitoring Setup?

Qdrant Monitoring Setup fits situations like: someone asks how to set up monitoring; prometheus config; grafana dashboard; health check endpoints.

How do I install Qdrant Monitoring Setup in Claude Code?

Run `npx skills add qdrant/skills --skill qdrant-monitoring-setup -a claude-code`. Or copy the skill folder (skills/qdrant-monitoring/setup in qdrant/skills) into .claude/skills/qdrant-monitoring-setup in your project. Claude Code loads it when a task matches its description.

How do I install Qdrant Monitoring Setup in Codex?

Run `npx skills add qdrant/skills --skill qdrant-monitoring-setup -a codex`. Or copy the skill folder (skills/qdrant-monitoring/setup in qdrant/skills) into .agents/skills/qdrant-monitoring-setup in your project. Codex loads it when a task matches its description.

Can I use Qdrant Monitoring Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qdrant/skills --skill qdrant-monitoring-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qdrant-monitoring-setup, .gemini/skills/qdrant-monitoring-setup, .github/skills/qdrant-monitoring-setup and .opencode/skills/qdrant-monitoring-setup in your project.

What does Qdrant Monitoring Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Qdrant Monitoring Setup is instructions for the agent only.

Does Qdrant Monitoring Setup access the network?

SKILL.md names 2 domains. As links in the text: skills.qdrant.tech and github.com. This is read from the text; nothing was executed.

Is Qdrant Monitoring Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qdrant Monitoring Setup use?

Qdrant Monitoring Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qdrant Monitoring Setup use?

About 874 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qdrant Monitoring Setup?

Skills that share tags, products or a category with Qdrant Monitoring Setup: Alloy (grafana/skills, 281 stars), Qdrant Monitoring (github/awesome-copilot, 40k stars), Prometheus Grafana (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars) and Grafana Dashboard (pando85/kaniop, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qdrant Monitoring Setup?

qdrant (a GitHub organization, an official publisher) maintains it in qdrant/skills, which has 254 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.

Source: qdrant/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Qdrant Monitoring Setup

Install Qdrant Monitoring Setup

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

How to Set Up Qdrant Monitoring

Prometheus Metrics

Hybrid Cloud Scraping

Liveness and Readiness Probes

Alerting

Log Centralization and Audit Logging

What NOT to Do

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

Alloy