docs(cloudflare): Add information about AI bindings - #18781
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
andreiborza
approved these changes
Jul 21, 2026
|
|
||
| The Workers AI instrumentation does **not** infer the conversation ID automatically. To group multi-turn AI calls into a single <Link to="/ai/monitoring/conversations/">Conversation</Link>, set it manually with <PlatformLink to="/configuration/apis/#setConversationId">`Sentry.setConversationId()`</PlatformLink>. The ID is applied as the `gen_ai.conversation.id` attribute to all AI spans within the current scope. See <PlatformLink to="/ai-agent-monitoring/#tracking-conversations">Tracking Conversations</PlatformLink> for details. | ||
|
|
||
| When you use the [Cloudflare Agents SDK](https://developers.cloudflare.com/agents/), each agent instance already has a stable identifier — its Durable Object instance name (`this.name`) — which is a natural conversation ID. |
Member
There was a problem hiding this comment.
giga-nit: Can we drop the emdashes? 😅
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
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.
DESCRIBE YOUR PR
This adds some information for Agent instrumentation. The conversation id still needs to be set manually (which idk, will change based on the architecture), but it is better than no documentation about the conversation id
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES