‹ 首页

qdrant-monitoring-setup

@qdrant · 收录于 1 周前 · 上游提交 昨天★ 社区精选

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

适合你,如果正在部署 Qdrant 并需要完整的监控方案

/ 通过 npx 安装 校验哈希
npx oh-my-skill add qdrant/skills/qdrant-monitoring-setup
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- qdrant/skills/qdrant-monitoring-setup
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify qdrant/skills/qdrant-monitoring-setup
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
GitHub stars
~691上下文体积 · 单文件
索引托管

怎么用

技能原文 SKILL.md作者撰写 · Apache-2.0 · 5ea598d

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)
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。