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

Fetch tracing

Pull traces from observability backends and normalize them for assure.

Fetch tracing pulls traces from the customer's observability stack and normalizes them into one canonical schema.

Works today

  • Langfuse pull → normalize → Gateway via the Langfuse bridge
  • Shared normalizer understanding common message/turn shapes
  • Export helpers for Studio paste

Planned connectors

In-product “connect Langfuse / Phoenix” buttons are coming soon. Until then, use the scripted Langfuse bridge or paste normalized payloads into Assurance.

Tracing

Capture correlated traces from the SUT for later assurance.

Assure

Deterministic, evidence-backed scoring against built-in or custom rubrics.

On this page

Works todayPlanned connectors