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
If I remember correctly this was part of Tracing without Performance and allows users to start or continue a trace without having to rely on transactions. I actually don't know about the current state of this feature, maybe @cleptric has some insights?
I see, so this just stores the sentry-trace and baggagein the propagation context so that it can be extracted later to form headers for any downstream requests.
Maybe sufficient to document this in the public facing API so that SDK users can more easily understand which methods they should be calling then.
Originally posted by @jamescrosswell in #3836
The SDK includes a
StartOrContinueTrace
method that returns a transaction context but doesn't use that context to start a new transaction...sentry-dotnet/src/Sentry.AspNet/HttpContextExtensions.cs
Lines 60 to 130 in 3e70c31
Under the hood, this propagates trace headers even when performance is disabled:
sentry-dotnet/src/Sentry/Internal/Hub.cs
Lines 252 to 253 in 3fde00a
Later this information gets used when forming headers for outbound requests:
sentry-dotnet/src/Sentry/Internal/Hub.cs
Lines 200 to 211 in 3fde00a
That intent should be clearly documented in the summary for the
StartOrContinueTrace
method.The text was updated successfully, but these errors were encountered: