docs: add Pydantic Logfire guide for Hindsight tracing#1339
Merged
nicoloboschi merged 2 commits intomainfrom Apr 30, 2026
Merged
docs: add Pydantic Logfire guide for Hindsight tracing#1339nicoloboschi merged 2 commits intomainfrom
nicoloboschi merged 2 commits intomainfrom
Conversation
Hindsight already emits OpenTelemetry spans for retain / recall / reflect (plus their LLM sub-spans) via the existing OTLP HTTP exporter. Logfire is an OTel-native receiver, so wiring it up is three env vars — no code changes, no new dependency. - New /developer/logfire guide page: env-var config, what the trace tree looks like, pairing with logfire.instrument_pydantic_ai(), useful Logfire queries, and troubleshooting - Cross-link from the existing Distributed Tracing section in monitoring.md so Logfire sits next to Langfuse / DataDog / Honeycomb in the supported backends list
nicoloboschi
requested changes
Apr 30, 2026
Collaborator
nicoloboschi
left a comment
nicoloboschi
left a comment
There was a problem hiding this comment.
can we have a blog post instead of a fixed page for the logfire setup? it's just about setting up logfire, not really hindsight
let's keep only the monitoring change + a new blog post when you have time
Per Nicolò's review on this PR — the dedicated /developer/logfire page was mostly Logfire setup, not Hindsight. Keeping only the one-line mention in the existing OTLP-backends list in monitoring.md, with the link pointing to logfire.pydantic.dev directly. The setup walkthrough, query examples, and troubleshooting moved into the companion blog post (hindsight-marketing-content#113).
Contributor
Author
|
Done — pushed 3d97ccb:
The Logfire-specific setup walkthrough (3 env vars), query examples, and troubleshooting all moved into the companion blog post: vectorize-io/hindsight-marketing-content#113. PR #1339 is now genuinely a Hindsight-side change only. |
nicoloboschi
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Logfire "integration" is a configuration guide pointing the existing OpenTelemetry exporter at Logfire's OTLP endpoint — no Logfire-specific code, no new dependencies, no integration package changes.
Hindsight already emits the right spans server-side (
hindsight.retain,hindsight.recall,hindsight.reflect, plus their LLM sub-spans following GenAI semantic conventions). Logfire is just another OTLP receiver alongside Langfuse / DataDog / Honeycomb.Changes
hindsight-docs/docs/developer/logfire.md:logfire.instrument_pydantic_ai()so agent.run nests Hindsight spanshindsight-docs/docs/developer/monitoring.mdso Logfire appears in the supported-backends list with a link to the new pageCompanion content
A blog post version of this lands separately in
hindsight-marketing-contentfor cross-publication on Pydantic's blog (per the collaboration with Laís Carvalho).