langfuse

Topics in the source

• Langfuse
• Route the task
• Evidence and mutation boundaries

Use Langfuse evidence to move from a broad symptom to the relevant trace, observation, session, prompt, or dataset. Start with the narrowest read-only query that can locate the event, then inspect its concrete inputs, outputs, timing, and errors. For trace, observation, exception, latency, or session diagnosis, read diagnostic and management workflows. For installation, credentials, tool groups, output defaults, connection failures, or empty results, read setup. For exact parameters, filters, pagination, output modes, and response shapes, read the tool reference. A common investigation starts with fetchtraces(age=60) or findexceptions(age=1440, groupby="file"), then fetches the selected trace or observation by ID. Use fulljsonfile only when the complete payload is needed; exports can contain sensitive user data. Treat model names, prompts, timestamps, and other values in historical traces as recorded evidence. Do not rewrite or normalize old model identifiers to a current name such as gpt-6-astra. Trace discovery and inspection are read-only. Prompt creation or relabeling, dataset changes, annotation-queue changes, and deletions mutate Langfuse; perform them only when the user requ

This is an excerpt. Refer to the complete source and its current requirements.