{"version":"2.1.314","anchor":"telemetry-additions","canonical_anchor":"telemetry-additions","heading":"Bedrock setup gains a guardrail trace option","tier":"use","area":"Bedrock","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/telemetry-additions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Bedrock setup gains a guardrail trace option\n\nBedrock configuration accepts a new guardrail_trace option, and a few internal usage-reporting fields were added\n\n**Unclear.** Where and how a user sets `guardrail_trace` is not stated.\n\n**What**\n\nThree small additions:\n\n- `guardrail_trace` is a new option in the configuration for Amazon Bedrock, the cloud service through which some people reach Claude. Setting it turns on guardrail tracing for Bedrock requests.\n\n- One internal usage event about launching background work now also records whether the program it needed was present.\n\n- Two more fields, `response_pair` and `response_pair_vote`, are now allowed in Claude Code's internal usage reporting.\n\n**Why**\n\nOnly the Bedrock option is something you can set yourself. The other two additions affect what Claude Code reports about its own operation and change nothing you do.\n\n- Area: Bedrock\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}