Best for
- 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'.
Source profileQuality 77/100
github/awesome-copilot/skills/qdrant-monitoring/setup/SKILL.md
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'.
- Source repository stars
- 37,126
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Get Prometheus scraping working first, then health probes, then alerting. Do not skip monitoring setup before going to production.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/github/awesome-copilot --skill "skills/qdrant-monitoring/setup"Safe inspection promptEditorial
Inspect the Agent Skill "qdrant-monitoring-setup" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/qdrant-monitoring/setup/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Prometheus Metrics
Use when: setting up metric collection for the first time or adding a new deployment.
Node metrics at /metrics endpoint Monitoring docsCluster metrics at /sysmetrics (Qdrant Cloud only)Prefix customization via service.metricsprefix config or QDRANTSERVICEMETRICSPREFIX env var - 02
Hybrid Cloud Scraping
Use when: running Qdrant Hybrid Cloud and need cluster-level visibility.
Hybrid Cloud Prometheus setup tutorial Hybrid Cloud PrometheusOfficial Grafana dashboards Grafana dashboard repoUse when: running Qdrant Hybrid Cloud and need cluster-level visibility. - 03
Liveness and Readiness Probes
Use when: configuring Kubernetes health checks.
Use /healthz, /livez, /readyz for basic status, liveness, and readiness Kubernetes health endpointsUse when: configuring Kubernetes health checks.- Use /healthz, /livez, /readyz for basic status, liveness, and readiness Kubernetes health endpoints - 04
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 monitoringUse AlertmanagerConfig to route alerts to Slack, PagerDuty, or other targets based on labelsAt minimum, alert on: optimizer errors, node not ready, replication factor below target, disk usage 80%
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 77/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 37,126 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- github/awesome-copilot
- Skill path
- skills/qdrant-monitoring/setup/SKILL.md
- Commit
- 9933dcad5be5caeb288cebcd370eeeb2fc2f1685
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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
/metricsendpoint Monitoring docs - Cluster metrics at
/sys_metrics(Qdrant Cloud only) - Prefix customization via
service.metrics_prefixconfig orQDRANT__SERVICE__METRICS_PREFIXenv 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,/readyzfor 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.formattojsonin 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_metricson 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)