AutoGineer
Generated banner for Qdrant Monitoring Setup
Generated logo for Qdrant Monitoring Setup

Qdrant Monitoring Setup

QdrantOfficialPublished by Qdrant

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Guides Qdrant monitoring setup including Prometheus scraping, Datadog integration, health probes, Hybrid Cloud metrics, alerting, and log centralization. Use when someone asks 'how to set up monitoring', 'Prometheus config', 'send metrics to Datadog', 'Grafana dashboard', 'health check endpoints', 'how to scrape Hybrid Cloud', 'what alerts to set', 'how to centralize logs', or 'audit logging'.
— the description by Qdrant

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides comprehensive guidance on setting up observability for Qdrant, covering metric collection via Prometheus and Datadog, Kubernetes health probes, and log management. It addresses specific requirements for self-hosted and Hybrid Cloud environments, including best practices for audit logging and alert configuration to ensure visibility into cluster health and operational state.

What it does

  • Explains how to configure Prometheus and Datadog for Qdrant metric collection.
  • Details the use of health check endpoints for Kubernetes liveness and readiness probes.
  • Provides instructions for monitoring Hybrid Cloud deployments, including cluster-exporter and operator metrics.
  • Outlines essential alert criteria for node and cluster health.
  • Describes methods for log centralization and audit log configuration across different versions.

When to use it

  • When setting up metric collection for a new Qdrant deployment.
  • When configuring Kubernetes health checks for Qdrant pods.
  • When establishing alerting rules for cluster issues like disk usage or replication status.
  • When implementing centralized logging or audit trails for compliance requirements.

Advantages

  • Provides clear guidance on distinguishing between self-hosted and Hybrid Cloud monitoring needs.
  • Offers specific configuration advice for modern audit log streaming.
  • Helps avoid common pitfalls like misinterpreting page cache memory usage.
  • Centralizes operational knowledge for Qdrant observability.

Usage examples

“How do I set up Prometheus monitoring for my Qdrant instance?”
The agent provides steps for scraping the /metrics endpoint and configuring the metrics prefix.
“What are the recommended health check endpoints for Qdrant in Kubernetes?”
The agent identifies /healthz, /livez, and /readyz as the appropriate endpoints for liveness and readiness probes.
“How can I centralize my Qdrant audit logs?”
The agent explains how to configure audit output to stdout or stderr for log collection via DaemonSets.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/qdrant/qdrant-monitoring-setup/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip qdrant-monitoring-setup.zip -d .agents/skills

Documentation by Qdrant

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

  • Datadog integration: collect metrics via the OpenMetrics /metrics endpoint Datadog integration

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.

  • 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/) by default. On v1.20 or newer, set audit.output to stdout, stderr, file_and_stdout, or file_and_stderr (env var QDRANT__AUDIT__OUTPUT) so a DaemonSet can collect them with no sidecar or Persistent Volume. Each line carries "kind": "audit" to tell it from regular logs, and the /audit/logs API returns nothing on a node that writes only to a stream. On v1.19 or older, mount a Persistent Volume and deploy a sidecar container to tail the files to stdout. 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

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Qdrant
Publisher
Qdrant (Official)
Source
qdrant/skills · skills/qdrant-monitoring/setup · commit 9f55f6a
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Qdrant or Qdrant.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download qdrant-monitoring-setup.zip