Qdrant Monitoring Setup logo

Qdrant Monitoring Setup

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

Overview

Publisherqdrant
Repositoryskills
Skill nameqdrant-monitoring-setup
Stars
262
Forks
31
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by qdrant on GitHub. Read the source before you install it.

Installation

Install the Qdrant Monitoring Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/qdrant/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/qdrant-monitoring/setup .claude/skills/qdrant-monitoring-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qdrant Monitoring Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Qdrant Monitoring Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Qdrant Monitoring Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

  • 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)

Frequently asked questions

What does the Qdrant Monitoring Setup AI skill do?

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

Why use Qdrant Monitoring Setup on TypingMind?

Because you install it once and use it with any model. Qdrant Monitoring Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Qdrant Monitoring Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/qdrant/skills/tree/main/skills/qdrant-monitoring/setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Qdrant Monitoring Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Qdrant Monitoring Setup?

As many as you like. As long as a model supports skills, you can use Qdrant Monitoring Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Qdrant Monitoring Setup AI skill free?

Yes. It is published on GitHub by qdrant under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇