Product engineer building AI into enterprise products. Build logs.
Product engineer building AI into enterprise products. Contracted to Facelift since 2019: I built the AI chat assistant in its Analyze product, and I'm building its successor in FDS (Facelift Data Studio). On the side I build dairy-agent, an open-source farm management agent for the dairy I run (Angular, AG-UI, self-hosted Langfuse/OTel). I write about what happens when you put an LLM behind a real UI: the protocol decisions, the failure modes, the observability you didn't know you'd need. No tutorials, just build logs.
Markdown supported · ⌘↵ to post
Kartik N V J K
Keeping instrumentation one level below the AG-UI event stream, so a third transport inherits tracing for free, is a clean call. I have hit the same approval-boundary issue where a pause and its resume split into two disconnected traces, and stable session keying is the only thing that makes latency there measurable. Are you capturing human wait time separately from model latency in that session?