qdrant-monitoring-debugging

# How to Debug Qdrant with Metrics First check optimizer status. Most production issues trace back to active optimizations competing for resources. If optimizer is clean, check memory, then request metrics. ## Optimizer Stuck or Too Slow Use when: optimizer running for hours, not finishing, or showing errors. - Use `/collections/{collection_name}/optimizations` endpoint (v1.17+) to check status [Optimization monitoring](https://skills.qdrant.tech/md/documentation/ops-optimization/optimizer/?s=optimization-monitoring) - Query with optional detail flags: `?with=queued,completed,idle_segments` - Returns: queued optimizations count, active optimizer type, involved segments, progress tracking - Web UI has an Optimizations tab with timeline view and per-task duration metrics [Web UI](https://skills.qdrant.tech/md/documentation/ops-optimization/optimizer/?s=web-ui) - If `optimizer_status` shows an error in collection info, check logs for disk full or corrupted segments - Large merges and HNSW rebuilds legitimately take hours on big datasets. Check progress before assuming it's stuck. ## Memory Seems Too High Use when: memory exceeds expectations, node crashes with OOM, or memory keeps growing. - Process memory metrics available via `/metrics` (RSS, allocated bytes, page faults) - Qdrant uses two types of RAM: resident memory (data structures, quantized vectors) and OS page cache (cached disk reads). Page cache filling available RAM is normal. [Memory article](https://skills...