feat: add metrics and usage to conversation streaming responses#3148
Draft
pjkroker wants to merge 12 commits intoaws-amplify:mainfrom
Draft
feat: add metrics and usage to conversation streaming responses#3148pjkroker wants to merge 12 commits intoaws-amplify:mainfrom
pjkroker wants to merge 12 commits intoaws-amplify:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 5c1bcbf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
7bee268 to
beb71bd
Compare
…SerializedStreamingResponseChunk type
beb71bd to
5c1bcbf
Compare
This was referenced Mar 30, 2026
Draft
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.
Problem
Streaming conversation responses from the Bedrock Converse API do not expose model usage or latency information. Consumers have no way to track token consumption or response latency for conversation turns.
Issue number, if available: #2355
Related PRs (all required for #2355)
This feature spans 4 repositories. PRs should be merged in this order:
AmplifyAIMetrics/AmplifyAIUsageGraphQL types and updates resolversChanges
metrics(latencyMs) andusage(inputTokens,outputTokens,totalTokens) fields to theStreamingResponseChunktype, included in the final chunk when a turn completes.metadatastream chunk inBedrockConverseAdapter.metricsandusageto JSON strings inConversationTurnResponseSenderbefore sending to AppSync.metricsandusageto the GraphQL message selection set inConversationMessageHistoryRetriever.MockMetricsandMockUsagecustom types onConversationMessageAssistantResponse.Corresponding docs PR, if applicable:
Validation
includes metrics and usage in the final streaming chunk(bedrock converse adapter)serializes metrics and usage to JSON when streaming(response sender)@aws-amplify/ai-constructspassChecklist
run-e2elabel set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.