Initialize the Logger
Configure detection types and sampling without leaving this page.
Hallucination Detection
See how Quotient scores extrinsic hallucinations.
Document Relevance
Measure whether retrieved documents support an answer.
Polling & Results
Retrieve detection results via the SDK.
What are Detections?
Detections are asynchronous analyses that run whenever you ship logs or traces to Quotient. They continuously score outputs for hallucinations, document relevance, and other reliability risks so you can intervene before they impact users. Once configured, detections execute in the background. You can review outcomes in the dashboard or poll for them programmatically.Why enable detections
- Catch issues fast: surface hallucinations or irrelevant context without manually reviewing transcripts.
- Quantify reliability: trend hallucination rate and document relevance over time or by tag.
- Prioritize fixes: combine detection scores with tags (model version, customer tier) to see where to invest engineering time.
Keep
detection_sample_rate
high during development to observe every interaction. Dial it down in production once metrics stabilize.Configure detections in three steps
- Initialize the logger with the detection types and sample rate that make sense for your workload.
- Send logs or traces that include the user prompt, model output, and supporting evidence.
- Review the results in the dashboard or via the SDK once detections finish processing.
Initialize the Logger with Detections
Enable detections during logger initialization:Send logs with detections enabled
After initialization, send logs that include the user query, model output, and any documents, instructions, or message history you want Quotient to evaluate.Interpret detection outcomes
Each detection result is attached to the originating log. In the dashboard you can:- Inspect hallucination highlights and see which sentences lack evidence.
- Review document relevance scores to spot noisy retrieval results.
- Filter by tags (environment, customer, model) to zero in on problematic slices.
Combine detections with Reports to move from single-log triage to trend analysis.
