Skip to content
Skill

Qdrant monitoring setup

Guides setting up Prometheus scraping, health probes, alerting and logs for Qdrant

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
41.3K
Last commit
2 days ago
License
MIT
Listing updated
1 day ago

Similar skills

About Qdrant monitoring setup

Qdrant monitoring setup is an open-source agent skill for knowledge and memory. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

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'.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (3 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Check another skill before you install it.

Install

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

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.

Claude Code docs on skills

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

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.

Codex docs on skills

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

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.

Cursor docs on skills

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

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.

Gemini CLI docs on skills

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

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.

VS Code docs on skills

Get the folder:

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.

The SKILL.md format

What it does

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

Qdrant monitoring setup 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 Skill creator, Rea changelog update, Rea tool design, Rea analysis optimization and Rea ci tests audit.

Where this comes from

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

More from github/awesome-copilot

  1. A DevOps checklist for deploys, Docker, Kubernetes, CI/CD, rollback and mobile releases

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Guides Qdrant scaling when data outgrows a node: tenants, time windows or sharding

    • Open source
    • 41.3K GitHub stars
    • Knowledge and memory
  3. Explains Qdrant's per-shard query subsampling for large limits across many auto-shards

    • Open source
    • 41.3K GitHub stars
    • Knowledge and memory
  4. Creates, exports and appends to Arize evaluation datasets using the ax command line

    • Open source
    • 41.3K GitHub stars
    • AI models and LLM tooling
  5. Creates Arize LLM-as-judge evaluators and runs them on traces or experiment results

    • Open source
    • 41.3K GitHub stars
    • AI models and LLM tooling
  6. Runs a model over an Arize dataset, saves the results as an experiment and compares runs

    • Open source
    • 41.3K GitHub stars
    • AI models and LLM tooling

Alternatives to Qdrant monitoring setup

  1. Guides an agent through drafting, testing and tuning new agent skills with measured evals

    • Free
    • 196K GitHub stars
    • AI models and LLM tooling
  2. Rewrites REA release notes from pinned Git history with verified contributor credit

    • Open source
    • 465K GitHub stars
    • Developer tools
  3. Audits and designs REA investigation tools, CLI and MCP contracts and Evidence semantics

    • Open source
    • 465K GitHub stars
    • Design and media
  4. Finds and fixes wasted work in REA analysis code while verifying results stay equivalent

    • Open source
    • 465K GitHub stars
    • Developer tools
  5. Audits REA CI workflows and test suites for false passes, fixture drift and wasted time

    • Open source
    • 465K GitHub stars
    • Developer tools
  6. Reverse engineers binaries, apps and firmware with REA and builds web app environments

    • Open source
    • 465K GitHub stars
    • Security