Repository navigation
Evaluation: Scope tracing opt-in to request paths, keep evaluations always-traced #1042
Description
Is your feature request related to a problem?
The recent PR #996 applied Langfuse tracing enable/disable across the entire codebase, affecting the evaluation pipeline. This broke scoring for evaluations that rely on managed LLM traces, causing scores to fail to populate when tracing was disabled.
Describe the solution you'd like
- Scope the enable/disable flag to only the request paths (llm-call, llm-chain, responses).
- Ensure evaluations are always traced, regardless of the project setting.
- Clean up the leftover gating logic from PR feat(langfuse): Add tracing opt-in/opt-out support #996.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Langfuse: Fix tracing only for request path (llm-call, llm-chain, responses) not for evaluation[/-][+]Evaluation: Fix tracing for scores[/+][-]Evaluation: Fix tracing for scores[/-][+]Evaluation: Scope tracing opt-in to request paths, keep evaluations always-traced[/+]github-actions commentedon Jul 13, 2026
🎉 This issue has been resolved in version 1.4.0-main.2 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀