This repository was archived by the owner on Oct 16, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 16, 2026. It is now read-only.
feat(dashboard): root cause explorer — trace-driven failure diagnosis #786
Description
Status Update (2026-04-05)
This issue is deprioritized for now.
AgentV already supports OTLP / OpenTelemetry export, including Langfuse, which covers much of the deep trace-analysis and root-cause workflow this issue was aiming to build into Studio.
Current Position
Studio should not try to become a full in-product trace-analysis platform unless there is a concrete unmet need beyond existing external observability tooling.
Deprioritized scope
- failure clustering UI in Studio
- side-by-side trace root-cause explorer in Studio
- git-correlation-heavy analysis views in Studio
- built-in fix-suggestion workflow in Studio
If revisited later, prefer a lightweight approach that links or layers on top of existing trace/export data instead of recreating a Langfuse-like product inside AgentV.
Activity
christso commentedon Jun 19, 2026
Closing as no longer aligned with the current strategy. Deep trace-driven diagnosis belongs in Phoenix or other post-run trace tooling layered over AgentV artifacts, not in the local Dashboard. The retained Dashboard role is fast zero-infra local inspection and comparison.