langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-21 20:05:30 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #1473] [CLOSED] Add cross workspace tracing #1597

New Issue
Closed
opened 2026-02-17 17:22:31 -05:00 by yindo · 0 comments
yindo commented 2026-02-17 17:22:31 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/1473
Author: @victorm-lc
Created: 11/17/2025
Status: ❌ Closed

Base: main ← Head: vic/add-cross-workspace-tracing

📝 Commits (1)

  • 930a490 add cross workspace tracing

📊 Changes

1 file changed (+333 additions, -0 deletions)

View changed files

📝 src/langsmith/log-traces-to-project.mdx (+333 -0)

📄 Description

Overview

Adding context on how to dynamically route traces to different LangSmith workspaces at runtime. This includes documentation for generic cross-workspace tracing in applications and overriding the default workspace for LangSmith deployments.

Type of change

Type: Update existing documentation

Related issues/PRs

  • GitHub issue: N/A
  • Feature PR: N/A

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

This PR adds a new section to src/langsmith/log-traces-to-project.mdx titled "Set the destination workspace dynamically" which covers two main use cases:

  1. Generic cross-workspace tracing: For applications that need to dynamically route traces to different workspaces based on runtime logic (e.g., customer ID, tenant, environment)
  2. Override default workspace for LangSmith deployments: For deployed agents where the default workspace needs to be overridden using graph lifespan context managers

Both Python and TypeScript code examples are provided for each use case, demonstrating the use of tracing_context/withTracing and workspace-specific LangSmith clients.

This documentation is particularly useful for multi-tenant applications that need to isolate traces by customer, environment, or team at the workspace level.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/1473 **Author:** [@victorm-lc](https://github.com/victorm-lc) **Created:** 11/17/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `vic/add-cross-workspace-tracing` --- ### 📝 Commits (1) - [`930a490`](https://github.com/langchain-ai/docs/commit/930a49013f93884077247983e36c75d06a0e658a) add cross workspace tracing ### 📊 Changes **1 file changed** (+333 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/log-traces-to-project.mdx` (+333 -0) </details> ### 📄 Description ## Overview Adding context on how to dynamically route traces to different LangSmith workspaces at runtime. This includes documentation for generic cross-workspace tracing in applications and overriding the default workspace for LangSmith deployments. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: N/A - Feature PR: N/A <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: https://langchain.slack.com/archives/C089RDWTKU4/p1760470955955709 ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed (Internal team members only / optional): Create a preview deployment as necessary using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes This PR adds a new section to `src/langsmith/log-traces-to-project.mdx` titled "Set the destination workspace dynamically" which covers two main use cases: 1. **Generic cross-workspace tracing**: For applications that need to dynamically route traces to different workspaces based on runtime logic (e.g., customer ID, tenant, environment) 2. **Override default workspace for LangSmith deployments**: For deployed agents where the default workspace needs to be overridden using graph lifespan context managers Both Python and TypeScript code examples are provided for each use case, demonstrating the use of `tracing_context`/`withTracing` and workspace-specific LangSmith clients. This documentation is particularly useful for multi-tenant applications that need to isolate traces by customer, environment, or team at the workspace level. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-17 17:22:31 -05:00
yindo closed this issue 2026-02-17 17:22:31 -05:00
yindo changed title from [PR #1473] Add cross workspace tracing to [PR #1473] [CLOSED] Add cross workspace tracing 2026-06-05 18:13:51 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#1597
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?