Tagged “monitoring”
-
What to monitor on a vector database
The handful of signals that predict an incident, the ones that only confirm one, and why recall needs a synthetic probe rather than a metric.
-
When your vector database gets slow
A diagnosis order for rising query latency: read the percentile shape first, then memory, filters, segments, tombstones, and search parameters.
-
When ingest outruns indexing
Writes are accepted, the queue never drains, and fresh records are searched by brute force. How to spot indexing lag and how to apply backpressure.
-
Failing over to a vector store replica
A replica that has never served traffic is not a replica. What replication does and doesn't cover for a vector index, and how to rehearse the failover.
-
Auditing a collection against your system of record
The index and the source of truth drift apart quietly: orphaned vectors, missing chunks, stale copies. How to run a reconciliation and what to do with it.
-
Catching an embedding model change nobody announced
Query vectors from a new model version searched against an index built with the old one. Nothing errors, recall falls, and only a probe will tell you.