Quick start
get the exporter, prometheus, and grafana running in a few minutes.
requirements
- docker and docker compose
- a shell that can run make (optional, recommended)
- go 1.21+ if you want to run the exporter outside docker
local qdrant with docker
this mode starts a local qdrant container alongside the exporter. run from the qdrant-exporter/ folder:
shell
set -a
source .env.local
set +a
docker compose --profile local up -d --buildor with the makefile shortcut:
bash
make localthis starts four services:
qdrant— vector db on 6333exporter— go exporter on 9999prometheus— scraper on 9091grafana— dashboards on 3000
qdrant cloud with docker
skip the local qdrant container and point the exporter at your cloud cluster instead.
.env.cloud
QDRANT_URL=https://your-cluster.qdrant.io
QDRANT_API_KEY=your_api_key_hereshell
set -a
source .env.cloud
set +a
docker compose up -d --buildor with make:
bash
make clouddo not enable the local profile
leaving out--profile local keeps the qdrant container out of the stack and the exporter will talk directly to your cloud cluster.run the exporter natively
if you'd rather skip docker and run the go binary directly, set the env vars and run:
bash
export QDRANT_URL=https://your-cluster-url
export QDRANT_API_KEY=your_api_key
go run .verify it works
open these urls once the stack is up:
- exporter metrics — http://localhost:9999/metrics
- prometheus ui — http://localhost:9091/graph
- prometheus targets — http://localhost:9091/targets
- grafana — http://localhost:3000 (admin / admin)
prometheus port gotcha
use port9091 for the host-mapped prometheus ui. port 9090 is the container's internal port and won't work from your browser.data persistence
- qdrant data lives in the named docker volume
qdrant-storage - collections survive
docker compose upanddocker compose down - running
docker compose down -vwill wipe them