Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
qdrant-monitoring - Skill - OpenSmartRoute
Skillv1.0.0
qdrant-monitoring
Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests…
Imported from qdrant/skills (skills/qdrant-monitoring/SKILL.md) via skills.sh. Install upstream with npx skills add qdrant/skills --skill qdrant-monitoring. Copyright stays with the author.
Qdrant Monitoring
Route first, then answer. Match the user's symptom in the table, Read that file, and answer from it.
Do not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.
The user says
Read
Want to set up Prometheus, Grafana, or health checks
setup/SKILL.md
Need to know which metrics to track
setup/SKILL.md
Setting up alerting, log centralization, or Hybrid Cloud metrics
setup/SKILL.md
Want to send Qdrant metrics to Datadog
setup/SKILL.md
Optimizer stuck or running forever
debugging/SKILL.md
Memory keeps growing in production
debugging/SKILL.md
Requests are slow and I need to find out why
debugging/SKILL.md
Is Qdrant healthy right now
debugging/SKILL.md
Want to find which queries are slow (slow request log)
debugging/SKILL.md
Need a per-collection memory or vector breakdown
debugging/SKILL.md
Qdrant monitoring tracks performance and health, and catches issues before they become outages. See the metric reference before tuning anything:
Monitoring docs
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Installed into a catalogue, chosen by a router
Install qdrant-monitoring and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
When a provider is down or over quota the request moves on; the trace says it did.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
qdrant-skills-qdrant-monitoring.ocm.jsonjson
{
"ocm": "1",
"id": "qdrant-skills-qdrant-monitoring",
"kind": "skill",
"name": "qdrant-monitoring",
"description": "Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis.",
"publisher": "qdrant",
"version": "1.0.0",
"capabilities": {
"domains": [
"observability",
"medical"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Guides Qdrant monitoring and observability setup. Use when someone asks 'how to monitor Qdrant', 'what metrics to track', 'is Qdrant healthy', 'optimizer stuck', 'why is memory growing', 'requests are slow', 'set up alerts', 'cluster health check', or needs to set up Prometheus, Grafana, health checks, or log centralization. Also use when debugging production issues that require metric analysis."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/qdrant/skills",
"path": "skills/qdrant-monitoring/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/qdrant/skills/qdrant-monitoring",
"key": "qdrant/skills/skills/qdrant-monitoring/SKILL.md"
},
"allowed_tools": [
"Read",
"Grep",
"Glob"
]
},
"instructions": "# Qdrant Monitoring\n\nRoute first, then answer. Match the user's symptom in the table, `Read` that file, and answer from it.\nDo not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.\n\n| The user says | Read |\n|---|---|\n| Want to set up Prometheus, Grafana, or health checks | `setup/SKILL.md` |\n| Need to know which metrics to track | `setup/SKILL.md` |\n| Setting up alerting, log centralization, or Hybrid Cloud metrics | `setup/SKILL.md` |\n| Want to send Qdrant metrics to Datadog | `setup/SKILL.md` |\n| Optimizer stuck or running forever | `debugging/SKILL.md` |\n| Memory keeps growing in production | `debugging/SKILL.md` |\n| Requests are slow and I need to find out why | `debugging/SKILL.md` |\n| Is Qdrant healthy right now | `debugging/SKILL.md` |\n| Want to find which queries are slow (slow request log) | `debugging/SKILL.md` |\n| Need a per-collection memory or vector breakdown | `debugging/SKILL.md` |\n\nQdrant monitoring tracks performance and health, and catches issues before they become outages. See the metric reference before tuning anything:\n[Monitoring docs](https://skills.qdrant.tech/md/documentation/ops-monitoring/monitoring/)",
"cost": {
"context_tokens": 299
}
}
Fetch it by URL: GET /api/v1/registry/qdrant-skills-qdrant-monitoring/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.