qdrant-monitoring-setup

github/awesome-copilot · skills/qdrant-monitoring/setup/SKILL.md

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

DevOps & CloudNo license★ 38398⑂ 4850commit f11a4e4

Install skillView source on GitHub

What this skill does

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.

Hybrid Cloud Prometheus setup tutorial Hybrid Cloud Prometheus
Official Grafana dashboards Grafana dashboard repo

Liveness and Readiness Probes

Use when: configuring Kubernetes health checks.

Use /healthz, /livez, /readyz for basic status, liveness, and readiness Kubernetes health endpoints

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)

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/setup · pinned to the source commit

# Run from your project root
git clone https://github.com/github/awesome-copilot.git .skillboard-tmp
git -C .skillboard-tmp checkout f11a4e441c5ff061b4f8ae37952be8c602e4034e
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/qdrant-monitoring/setup" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/github/awesome-copilot.git .skillboard-tmp
git -C .skillboard-tmp checkout f11a4e441c5ff061b4f8ae37952be8c602e4034e
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/qdrant-monitoring/setup" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/setup

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so qdrant-monitoring-setup is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit f11a4e441c5f. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

qdrant-monitoring-setup

github/awesome-copilot · skills/qdrant-monitoring/setup/SKILL.md

DevOps & CloudNo license★ 38398⑂ 4850commit f11a4e4

Install skillView source on GitHub

What this skill does

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.

Hybrid Cloud Prometheus setup tutorial Hybrid Cloud Prometheus
Official Grafana dashboards Grafana dashboard repo

Liveness and Readiness Probes

Use when: configuring Kubernetes health checks.

Use /healthz, /livez, /readyz for basic status, liveness, and readiness Kubernetes health endpoints

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)

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/setup · pinned to the source commit

# Run from your project root
git clone https://github.com/github/awesome-copilot.git .skillboard-tmp
git -C .skillboard-tmp checkout f11a4e441c5ff061b4f8ae37952be8c602e4034e
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/qdrant-monitoring/setup" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/github/awesome-copilot.git .skillboard-tmp
git -C .skillboard-tmp checkout f11a4e441c5ff061b4f8ae37952be8c602e4034e
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/qdrant-monitoring/setup" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/setup

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so qdrant-monitoring-setup is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit f11a4e441c5f. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

qdrant-monitoring-setup

What this skill does

How to Set Up Qdrant Monitoring

Prometheus Metrics

Hybrid Cloud Scraping

Liveness and Readiness Probes

Alerting

Log Centralization and Audit Logging

What NOT to Do

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits

qdrant-monitoring-setup

What this skill does

How to Set Up Qdrant Monitoring

Prometheus Metrics

Hybrid Cloud Scraping

Liveness and Readiness Probes

Alerting

Log Centralization and Audit Logging

What NOT to Do

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits