If you trace LLM calls in one tool and your app in another, agent runs that don't throw…
This is a dev post classified by Jev as Testing & observability (a tool drop), kept by the Dev Radar because it carries real work, not commentary.
If you trace LLM calls in one tool and your app in another, agent runs that don't throw errors are hard to debug. On Sep 30, we'll show how Pydantic Logfire puts the model call and the rest of the request in one OTel trace. Save your spot: https://pydantic.io/YKQo9
Posted by Pydantic (20.3k followers) 2 days ago · 21 likes · 1.2k views · view the original post on X. Kept by the Dev Radar as Testing & observability.
More dev work like this
- What does observability look like when a judgment costs nothing? — @hugorcd
- When agent traces turn into a debugging pile, this repo gives you a place to inspect them. — @DanKornas
- I’m glad @strawgate's standards for coffee are lower than his standards for code review… — @kayvz
- Gitar finds bugs, fixes them under your team's rules, and verifies every fix by running… — @SonarSource
- OPENAI 🔥: Chrome extensions are now supported in the ChatGPT desktop browser! — @testingcatalog
- AI at scale needs visibility to match. — @splunk
- Quick tip from Visual Studio on YouTube... See the Visual Studio Debugger Agent use a… — @VisualStudio
- Agent regressions are hard to catch when traces are read-only. — @DanKornas
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 12.2k posts from 4.7k X accounts over the last 21 days, 1.4k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 18:39 UTC. Full method.