Not all Sentry errors include a `correlation_id`
Seemingly we only include a correlation_id
tag when we use the Gitlab::Sentry.track_exception
method. I don't see it being added in the default Raven configuration, which is what gets used when the application unexpectedly raises an exception.
Is this intentional, or an oversight perhaps?
cc @twoodham because he was seeing this in @jarv's talk
cc @stanhu because he's Stan