How to use distributed tracing in your agent server #1961
Conversation
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
Contributor
|
Mintlify preview ID generated: preview-wfhage-1766013107-bdcc989 |
katmayb
approved these changes
Dec 18, 2025
Contributor
katmayb
left a comment
katmayb
left a comment
There was a problem hiding this comment.
Looks good, just a couple typos and some links, thanks!
|
|
||
| Distributed tracing links runs across services using context propagation headers: | ||
|
|
||
| 1. The **client** infers the trace context from the current run and sends it as HTTP headers |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. The **client** infers the trace context from the current run and sends it as HTTP headers | |
| 1. The **client** infers the trace context from the current run and sends it as HTTP headers. |
| Distributed tracing links runs across services using context propagation headers: | ||
|
|
||
| 1. The **client** infers the trace context from the current run and sends it as HTTP headers | ||
| 2. The **server** reads the headers and adds them to the run's config and metadata as `langsmith-trace` and `langsmith-project` configurable values. You can choose to use thes to set the tracing context for a given run when your agent is used. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. The **server** reads the headers and adds them to the run's config and metadata as `langsmith-trace` and `langsmith-project` configurable values. You can choose to use thes to set the tracing context for a given run when your agent is used. | |
| 2. The **server** reads the headers and adds them to the run's config and metadata as `langsmith-trace` and `langsmith-project` configurable values. You can choose to use these to set the tracing context for a given run when your agent is used. |
| <Tabs> | ||
| <Tab title="RemoteGraph"> | ||
|
|
||
| Set `distributed_tracing=True` when initializing `RemoteGraph`. This automatically propagates trace headers on all requests. |
Contributor
There was a problem hiding this comment.
Suggested change
| Set `distributed_tracing=True` when initializing `RemoteGraph`. This automatically propagates trace headers on all requests. | |
| Set `distributed_tracing=True` when initializing @[`RemoteGraph`]. This automatically propagates trace headers on all requests. |
| description: Unify traces when calling your deployed Agent Server from another service using RemoteGraph or the SDK. | ||
| --- | ||
|
|
||
| When you call a deployed Agent Server from another service, you can propagate trace context so that the entire request appears as a single unified trace in LangSmith. This uses LangSmith's [distributed tracing](/langsmith/distributed-tracing) capabilities, which propagate context via HTTP headers. |
Contributor
There was a problem hiding this comment.
Suggested change
| When you call a deployed Agent Server from another service, you can propagate trace context so that the entire request appears as a single unified trace in LangSmith. This uses LangSmith's [distributed tracing](/langsmith/distributed-tracing) capabilities, which propagate context via HTTP headers. | |
| When you call a deployed [Agent Server](/langsmith/agent-server) from another service, you can propagate trace context so that the entire request appears as a single unified trace in LangSmith. This uses LangSmith's [distributed tracing](/langsmith/distributed-tracing) capabilities, which propagate context via HTTP headers. |
| </Tab> | ||
| <Tab title="SDK"> | ||
|
|
||
| If you're using the LangGraph SDK directly, propagate trace headers manually using `run_tree.to_headers()`: |
Contributor
There was a problem hiding this comment.
Suggested change
| If you're using the LangGraph SDK directly, propagate trace headers manually using `run_tree.to_headers()`: | |
| If you're using the [LangGraph SDK](/langsmith/reference) directly, propagate trace headers manually using `run_tree.to_headers()`: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.