feat(bedrock): add request_metadata for per-request cost attribution#2338
Open
psantus wants to merge 1 commit into
Open
feat(bedrock): add request_metadata for per-request cost attribution#2338psantus wants to merge 1 commit into
psantus wants to merge 1 commit into
Conversation
…ibution Add request_metadata config option to BedrockModel that maps to the requestMetadata field in Converse/ConverseStream API requests. This enables per-request finops by attaching key-value tags (e.g. team, environment, feature) that appear in model invocation logs. Default behavior is unchanged (no metadata sent). When set, the dict is passed as-is to the Bedrock API. Ref: https://docs.aws.amazon.com/bedrock/latest/userguide/cost-mgmt-request-metadata.html
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.
Description
Add
request_metadataconfig option toBedrockModelthat maps to therequestMetadatafield in Converse/ConverseStream API requests.This enables per-request finops by attaching key-value tags (e.g. team, environment, feature) that appear in model invocation logs.
Default behavior is unchanged — no metadata is sent unless explicitly configured.
Usage
Reference
https://docs.aws.amazon.com/bedrock/latest/userguide/cost-mgmt-request-metadata.html
What was tested
test_format_request_with_request_metadata— metadata included when configuredtest_format_request_without_request_metadata— backward compat (no key when unset)