agentsclimarketplace
Sign in

Setup

Skill qdrant/skills/skills/qdrant-monitoring/setup

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 its SKILL.md

Install
npx -y skills add qdrant/skills --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.3 KB, 664 tokens by cl100k_base, as published. Nobody here has run it

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)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 664 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

  • Write the configuration filein 36 of 1553
  • Create the directory structurein 35 of 1553, across 33 files
  • Verify the setupin 31 of 1553, across 28 files
  • Run the setup scriptin 30 of 1553, across 29 files
  • Pre-determine the required sample sizein 29 of 1553, across 12 files
  • Check if the configuration already existsin 29 of 1553
  • Document every testin 26 of 1553, across 10 files
  • Start with a hypothesisin 26 of 1553, across 11 files
  • Ask one question at a timein 22 of 1553
  • Test a single variable per testin 21 of 1553, across 9 files
  • Read product marketing context before asking questionsin 19 of 1553, across 8 files
  • Do not peek and stop earlyin 18 of 1553, across 7 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.