Repository navigation
feat: instrument Inngest AgentKit execution - #2814
Draft
pear1-pea (pear1-pea) wants to merge 1 commit into
Draft
pear1-pea (pear1-pea) wants to merge 1 commit into
pear1-pea (pear1-pea) wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
AgentKit currently produces no Braintrust spans for network orchestration, agent runs, model inference, routing or tool execution. This adds automatic instrumentation for the verified ESM and CommonJS layouts of @inngest/agent-kit 0.13.2.
The implementation follows the normal interceptor/provider/config path. Spans retain stable names and record network, agent and tool names in metadata. Tool preparation covers createTool plus plain, Inngest-function and MCP tools before invocation. It preserves tool objects, receivers and extra arguments, and leaves already immutable/accessor-based handlers unchanged. Those immutable handlers may lack individual tool spans. A separate manual module wrapper is outside this initial automatic-instrumentation scope.
Validation performed locally:
Refs #2396