QAVE Studio Docs
QAVE Studio Docs
Sign inGet started — the Studio loop
Getting StartedFirst assurance runQuick assure
ConceptsLifecycleGlossaryHow QAVE Studio worksComing soon
Account & workspaceSignup and loginPeopleDemo creditsRolesSettings
Generate simulation suitesContext templatePII and field enhanceDimensionsAgents and plannerDraft review and Save
ExportExport formatsExport formats (detail)
Assurance SDKSDK overviewQAVE Studio suite fetch APIAgent and JSONL queueLangfuse bridge
Execute and tracesRecipe chatbot (reference SUT)TracingFetch tracing
AssureEvaluate APIRubrics and evidenceReading scores
History
WorkbenchGolden data
CoverageCoverage dashboardCoverage strategiesCoverage advisorTest case quality
RAG AssuranceRAG runsRAG datasetsRAG analytics
Project evalsError analysisUnderstanding scores
Studio guidesDimensionsTuplesConversation modesMulti-lingual testingWorkflowsHuman reviewBest practices
ReferenceAPI and packagesTroubleshooting
Execute & Traces

Tracing

Capture correlated traces from the SUT for later assurance.

Assurance needs structured evidence: messages, spans, tool calls, latency, and metadata keyed by a correlation ID (typically the case id).

Supported today

  • Langfuse emission from the reference SUT and from the SDK tracer
  • Local JSON / JSONL fallbacks for offline debugging
  • Studio paste of conversation or trace payloads

Correlation

Carry the originating case id on every trace so scores map back to suite, dimension, and intent.

OpenTelemetry

Full OTel instrumentation across the Studio pipeline is part of the broader observability story; tutorials in this wave focus on Langfuse because that path is operational for the reference loop.

Recipe chatbot (reference SUT)

Use the recipe-chatbot HTTP API as the canonical system under test for tutorials.

Fetch tracing

Pull traces from observability backends and normalize them for assure.

On this page

Supported todayCorrelationOpenTelemetry