Skip to content
Discussion options

You must be logged in to vote

You're not missing anything — the Model column shows the raw model string ingested from the trace, not the name of the matched model definition. Since your Bedrock calls report the application inference profile ARN as the model string, that ARN is what appears in the column, even though the definition matched correctly (which is why your costs are calculated and the observations show under the definition's model observations).(1)

Bedrock reporting region-prefixed inference profile IDs or full ARNs as the model string is expected behavior, and the fix for pricing is exactly what you did: a custom model definition whose regex match_pattern matches the exact string your traces report. User-d…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@CodeCLS
Comment options

CodeCLS Aug 20, 2026
Collaborator

@slawekp
Comment options

Answer selected by slawekp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants