Provide the expected destination URL for a Sentry event before it is sent

[nwhite-riot]

It is often frustrating to dig through recent crashes in Sentry to find your specific crash when you're debugging/reproducing something. If we could make it so that Sentry provided a log line with the expected destination of the Sentry event, it would short circuit all of the waiting.

[redxdev]

Seconding this - I imagine that the final URL depends on sentry's processing of the event, but some kind of short link that eventually redirects to the proper location once the event is processed would be an amazing feature.

We've taken to storing the unreal crash GUID as a tag to help lookup crashes in sentry (Sentry.SetTag(TEXT("CrashGUID"), FGenericCrashContext::GetCachedSessionContext().CrashGUIDRoot);, unreal prints this value near the top of every log so it's easy to find), but it'd be even better to have a direct link.

[bruno-garcia]

Having a. link can be tricky because with a DSN we don't know what org slug you're in. But, you can paste the event id and go straight to that event detail in Sentry

@tustanivsky for context: The event id is a guid defined client side. Often our CaptureEvent APIs return the Guid In some SDks we have Sentry.LastEventId which is useful to get the event id from event captured automatically.