Replies: 3 comments 2 replies
-
|
@hassiebp thoughts or comments? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Thanks for reply @nimarb and your interest!, have rough sketched something. Would love your thoughts on this |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@nimarb any thoughts??? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature or potential improvement
Add a "Causal Chain" visualization in LangFuse to link spans by input-output dependency. While LangFuse provides excellent trace inspection, developers currently have no way to see which upstream call or retrieved chunk led to a failure or hallucination. Understanding this causal link is crucial for debugging multi-step agent workflows (LangGraph, LangChain, DSPy, etc.).
Proposed Solution
parent_output_ref.failure_depthordependency_density.Additional information
I’d be glad to work on this feature end-to-end (schema changes + UI visualization). If this fits within the current roadmap, I can begin with a small prototype to validate the approach.
Beta Was this translation helpful? Give feedback.
All reactions