{"version":"2.1.288","anchor":"otel-raw-api-body-logging-can-withhold-bodies-and-redact-by","canonical_anchor":"otel-raw-api-body-logging-can-withhold-bodies-and-redact-by","heading":"Raw request and response logging can now leave message bodies out","tier":"use","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/otel-raw-api-body-logging-can-withhold-bodies-and-redact-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Raw request and response logging can now leave message bodies out\n\nOpenTelemetry logging of raw API bodies can now record that a body was withheld instead of logging it, and filters bodies through an account memory step\n\n**Unclear.** It is not clear what causes a body to be withheld, or what the account memory step does to the logged bodies.\n\n**What**\n\nClaude Code can send diagnostic data through OpenTelemetry, a standard way of passing usage and logging data to a monitoring system you set up. One option logs the raw text of each request sent to the API and each response that comes back. These are the message bodies.\n\nThat logging changed in two ways:\n\n- A body can now be withheld. The log then records that the body was withheld and not recorded, instead of the body itself.\n\n- Both the request body and the response body now pass through a step tied to account memory before they are logged. Before, the body was written to the log as it was.\n\n**Why**\n\nThis affects how much private content ends up in your telemetry logs if you have raw body logging turned on. Some logged bodies may now be missing or altered compared with before.\n\n- Area: Telemetry\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}