You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ A working example can be found in the `examples/cloudflare-worker` directory.
99
99
100
100
### Next.js / Vercel
101
101
102
-
Vercel provides a comprehensive OpenTelemetry integration through the `@vercel/otel` package. After following [their integration instructions](https://vercel.com/docs/otel), Add the following two env variables to your project:
102
+
Vercel provides a comprehensive OpenTelemetry integration through the `@vercel/otel` package. After following [their integration instructions](https://vercel.com/docs/otel), Add the following env variables to your project:
The above will point the instrumentation to Logfire.
111
111
112
+
> [!NOTE]
113
+
> The Vercel production deployments have a caching mechanism that might prevent the changes from taking effect immediately or spans being reported. If you are not seeing spans in Logfire, you can [clear the data cache for your project](https://vercel.com/docs/data-cache/manage-data-cache).
114
+
112
115
Optionally, you can use the Logfire API package for creating manual spans. Install the `@pydantic/logfire-api` NPM package and call the respective methods from your server-side code:
0 commit comments