cc @getsentry/team-javascript-sdks

SDK Changes Detected

The following PRs were merged to getsentry/sentry-javascript in the last 7 days that may affect the sentry-node-sdk skill:

• feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration sentry-javascript#19770 — feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration (feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration sentry-javascript#19770)

Potential Skill Gaps

1. New Config Option: nativeNodeFetchIntegration() now accepts a headersToSpanAttributes option to capture specific HTTP headers as span attributes. Example:

   Sentry.init({
     integrations: [
       Sentry.nativeNodeFetchIntegration({
         headersToSpanAttributes: {
           requestHeaders: ['x-request-id', 'x-custom-header'],
           responseHeaders: ['content-length', 'content-type'],
         },
       }),
     ],
   });

   This is especially relevant because response headers like content-length were previously captured automatically but became opt-in after @opentelemetry/instrumentation-undici@0.22.0. The skill's Config Reference does not mention any options for nativeNodeFetchIntegration.

Skill Files to Review

• skills/sentry-node-sdk/SKILL.md

Priority

MEDIUM — new opt-in configuration option that users may need to restore previously-automatic header capture behavior.

Generated by SDK Skill Drift Detector · ◷

• expires on Mar 30, 2026, 11:02 PM UTC