Sampling
Latitude does not sample traces before making them observable. If a trace is ingested and retained, it can appear in the Traces view, filters, search results, and manual review workflows.Latitude does not sample semantic search, exact-text search, or the trace stream used by automatic flaggers. Full coverage matters for rare failures, edge-case user behavior, and low-volume regressions.
Where sampling exists
Sampling only applies to selected downstream processing. It does not affect trace visibility or search coverage.Evaluation sampling
Evaluations can run on a percentage of matching incoming traces. This controls monitoring cost and volume while keeping traces available for search and review. A sampling rate of0% pauses the evaluation.
Flagger sampling
Flaggers evaluate whole sessions, so their sampling rate counts sessions rather than individual traces. The LLM-based flaggers sample how aggressively Latitude runs their model-backed checks, which balances detection coverage against AI usage. The deterministic flaggers (empty response, tool call errors, output schema validation, low cache hit rate) have no sampling control: they are free, so an enabled one runs on everything it is eligible for. When screening finds evidence pointing at a specific category, that flagger runs regardless of its sampling rate. Sampling governs the sessions where nothing stood out. Flagger sampling does not remove traces from search, filtering, or manual signal investigation.Related
- Search: Search across all searchable traces
- Evaluations: Monitor signal patterns on incoming traces
- Flaggers: Automatic detection for common failure categories