Agent monitoring cannot display the agents' execution traces, such as tool calls, inputs, outputs, etc.

[liumingliao]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Agent monitoring cannot display the agents' execution traces, such as tool calls, inputs, outputs, etc.
agents 监控 无法查看 agents的轨迹，就是工具调用、输入输出等

[dosubot[bot]]

Hi @liumingliao! I'm Dosu and I'm helping the Dify team.

This is a confirmed gap in the Agent V2 (new Agent app) monitoring UI. The Agent V2 log detail panel currently shows only conversation input/output and basic metadata (latency, tokens, timestamp) — it does not surface per-message execution traces such as tool calls, intermediate reasoning steps, or their inputs/outputs [1].

The backend does record this data, but the frontend formatAgentLogMessages function in the Agent V2 log detail panel does not wire up agent_thoughts or tool-call trace data, so it never reaches the UI [1].

There are also two related UI bugs on the log page:

• The small log icon on hover is visible and clickable but produces no dialog, because hideLogModal suppresses the modal without preventing the icon from rendering [1].
• Clicking the icon writes showPromptLogModal=true to a global store, which can cause a stale "Prompt Log" modal to appear on the Studio page after navigating away [2].

Note that this is specific to the new Agent app (Agent V2). If you use an Agent node inside a Workflow/Chatflow, the trace logs (tool calls, inputs, outputs) are supported and rendered via the AgentLogItem component and the agent log event pipeline [3].

A related issue tracking this missing per-message trace in the Agent V2 log UI was filed at #40761 — adding a thumbs-up there would help the team prioritize surfacing execution traces in the Agent V2 monitoring view.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.