Nauel I.

Commented on Questions About Langflow Trace Types and Latency M...·Posted inPhoenix Support

RunLLM Is there an explanation for why AgentExecutor traces are included in the project metrics? From what I can see, their inclusion can be misleading. Could you provide some intuition behind this behavior?

Commented on Questions About Langflow Trace Types and Latency M...·Posted inPhoenix Support

Nauel I.

RunLLM does applying a filter affect latency metrics at the project level? I tried using span_kind == "CHAIN", but it doesn’t seem to change the metrics at all. Is this expected behavior, or am I missing something?

Posted in Phoenix Support·

Nauel I.

Questions About Langflow Trace Types and Latency Metrics in Arize

Hi everyone, hope you’re all doing well 👋 I have a question about Langflow’s execution behavior and how it generates traces in Arize. From what I’ve observed, every time a flow runs, it produces two traces: • An AgentExecutor trace (OpenAI agent in my case) • A UUID trace (Langflow component trace) At first this seemed fine, but when I started looking at latency metrics (p50 & p99), I noticed that the AgentExecutor trace is also included in the calculations. My expectation was to track only the UUID traces, since they better represent the latency of each request to the Langflow service. A couple of questions: • Is it expected that AgentExecutor and UUID traces are mixed in latency calculations? • How can I track latency using only UUID traces? Thanks in advance — really appreciate any clarification!

5Comments