Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

Anthropic's own telemetry failures no longer look like your collector breaking

You'll notice
Useful3 Signal2
Telemetry

Anthropic's own telemetry failures are summarised separately so they don't look like your collector breaking.

What

The wrapper around Anthropic's internal metrics exporter now reports success on every path, including shutdown, credential errors, opt-out check failures, HTTP failures and thrown exceptions, and routes the error to a new aggregator instead. The first failure logs a single line that says explicitly the problem is Anthropic's pipeline and not your own OpenTelemetry collector, later failures are counted silently, and a single summary line is emitted at flush or shutdown.

Details
  • Because the export is reported as a success, your OTel collector no longer sees these as export errors to retry or report.
  • Only the wrapper around Anthropic's own exporter is affected; a collector you configure yourself is untouched.
  • All log lines from this exporter gained a shared prefix so they can be told apart from your own pipeline's output.
  • Present unconditionally in this build, with no flag or setting controlling it.
Evidence

export failed (${e}). This is Anthropic's own telemetry pipeline, not your OTel collector; further failures are counted and summarised at shutdown., This is Anthropic's own telemetry pipeline, not your OTel collector; further failures are counted and summarised at shutdown.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →