Skip to content

Commit 39009ec

Browse files
authored
docs: Adds OTEL info callout (#767)
1 parent d9b29f1 commit 39009ec

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/observability/how_to_guides/trace_with_vercel_ai_sdk.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,14 @@ Which results in a trace like [this one](https://smith.langchain.com/public/4d3a
124124

125125
### Node.js
126126

127+
:::note
128+
The official `@opentelemetry/sdk-node` client SDK is [currently experimental](https://github.com/open-telemetry/opentelemetry-js?tab=readme-ov-file#package-version-compatibility) and pushes breaking changes in minor version updates.
129+
130+
`@opentelemetry/[email protected]` is only fully supported if you have `langsmith>=0.3.22` installed.
131+
132+
If you are on an older version of `langsmith`, install the previous version, [`@opentelemetry/[email protected]`](https://www.npmjs.com/package/@opentelemetry/sdk-node?activeTab=versions) and `@opentelemetry/[email protected]`.
133+
:::
134+
127135
First, learn more how to setup OpenTelemetry instrumentation within your Node.js app [here](https://opentelemetry.io/docs/languages/js/getting-started/nodejs/#setup).
128136

129137
In particular, you will need to ensure that OTEL setup and configuration run before your application logic. One tool commonly used for this task are Node's [`--require`](https://nodejs.org/api/cli.html#-r---require-module) or `--import` flags.

0 commit comments

Comments
 (0)