Practical Notes
Weave is most valuable when you treat observability as a product feature. Add traces around every boundary: user input → prompt assembly → tool calls → validation → final output. Then use the trace tree to answer: where did latency come from, which step failed, and what data caused the failure?
Safety note: Avoid logging secrets; sanitize prompts and tool args before tracing in production.
FAQ
Q: What should I trace first? A: Start with your top-level agent run function and the model-call wrapper; then add ops around tools and validators.
Q: Does it only work with OpenAI? A: No. The README says you can trace any function, including calls to different providers and open-source models.
Q: How do I keep traces useful? A: Log structured inputs, normalize outputs, and capture error cases; traces are only helpful when they show failures clearly.