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
Before implementing for Native, consider/verify how scopes are stored in the Native SDK. Can they be AsyncLocal? If not, we don't want to add attachments from one AsyncLocal scope that get added to events from another AsyncLocal scope... in an ASP.NET Core app (native AOT), that could result in attachments relating to one request being added to events from other requests.
Originally posted by @jamescrosswell in #5038
Warning
Before implementing for Native, consider/verify how scopes are stored in the Native SDK. Can they be AsyncLocal? If not, we don't want to add attachments from one AsyncLocal scope that get added to events from another AsyncLocal scope... in an ASP.NET Core app (native AOT), that could result in attachments relating to one request being added to events from other requests.
See:
➡️ A possible solution to this is to limit the attachment sync to global scope mode.