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
{{ message }}
This repository has been archived by the owner on Dec 5, 2023. It is now read-only.
I attempted to enable tracing in my serverless application, but we have a high traffic application, which means that many invocations of both the same function and other functions are often running in parallel. Since the Sentry.configureScope() call is global, attempting to set a span for one instance overwrites spans enabled for previous instances. If there is a way to configure a separate scope for each function invocation, it should be documented, both in Sentry's Azure Functions SDK docs and in this examples repository.
The text was updated successfully, but these errors were encountered:
I attempted to enable tracing in my serverless application, but we have a high traffic application, which means that many invocations of both the same function and other functions are often running in parallel. Since the Sentry.configureScope() call is global, attempting to set a span for one instance overwrites spans enabled for previous instances. If there is a way to configure a separate scope for each function invocation, it should be documented, both in Sentry's Azure Functions SDK docs and in this examples repository.
The text was updated successfully, but these errors were encountered: