Seeing inside the machine
For months I debugged my outreach by clicking a node and reading its before and after. Here is what it takes to get that X-ray back for an AI pipeline.
For months I ran my outreach as an n8n workflow, and the thing I loved about it was not the automation. It was the debugging. When a draft came out wrong, I opened the last run, clicked the node that looked suspect, and there it was: the exact input on the left, the exact output on the right. Before and after, for every step. I could walk back node by node until I found the one that turned a good input into a bad output, and then I knew where to fix it.
Then I moved the real work into a product of my own, and the first thing I missed was not a feature. It was that X-ray. The pipeline still ran. It still produced drafts. But when one came out wrong I was back to guessing, because I could no longer see what each stage had been handed and what it had returned.
This is about getting that vision back for an AI pipeline, and about the one thing none of the tools will hand you.
Sources
- Langfuse self-hosting: a self-hosted instance sends no data to Langfuse Cloud (accessed 2026-09-29)langfuse.com
- Langfuse MIT license scope; /ee commercial features (accessed 2026-09-29)github.com
- Comet Opik: Apache-2.0 whole platform, Docker/K8s self-host, TS SDK + OTel (accessed 2026-09-29)github.com
- Arize Phoenix: self-host, Elastic License 2.0, OpenInference instrumentors (accessed 2026-09-29)github.com
- n8n Sustainable Use License (fair-code) terms (accessed 2026-09-29)docs.n8n.io
- n8n pin-and-mock data: Node Detail View input/output panels (accessed 2026-09-29)docs.n8n.io
- Datadog CloudPrem is logs-only (trace storage stays SaaS) (accessed 2026-09-29)datadoghq.com
- OpenTelemetry default 256-char attribute limit (2026-01-30)oneuptime.com
- OpenLLMetry: Apache-2.0 OpenTelemetry instrumentation for LLMs (accessed 2026-09-29)github.com