AgentSkillsCN

qdrant-monitoring-setup

诊断并修复Qdrant索引与数据摄入缓慢的问题。适用于有人报告“上传太慢”、“索引耗时太久”、“优化器卡住了”、“HNSW构建时间过长”或“数据上传了但搜索不好”时使用。也适用于优化器状态显示错误、片段无法合并，或索引阈值问题出现时使用。

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

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)