You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: honor faas.invocation_id from non-Lambda instrumentation scopes
Manual instrumentation that creates its handler span from a custom ActivitySource/Tracer (a scope not in the recognized AWS Lambda instrumentation list) had its faas.invocation_id ignored: process_trace_request only extracted the invocation id from spans in recognized Lambda scopes. With no id and no Runtime API proxy fallback, the receiver discarded the trace ("/v1/traces has no invocation IDs, discarding trace").
Extract faas.invocation_id from spans in any scope for invocation correlation. Handler-span rewrites (rename, kind, reparent) stay limited to recognized Lambda scopes, so non-Lambda spans are correlated but otherwise left untouched.
Refs: SUP-1255
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments