Raven manually captured exceptions aren't distinguishable from "normal" exceptions.

Problem

Gitlab::Logger.error manually captures exceptions, but doesn't identify them as manually captured. This can cause concern that a problem exists, when in reality the code is probably executing as "desired".

example: https://sentry.gitlab.net/gitlab/customersgitlabcom/issues/1118125/events/22686924/

Proposal

Provide more information using Raven's "context" feature. Possibly using tag/extra/logger.

Result

An exception captured in Sentry that is easily identified as "manually captured"

Next steps (if any)

Debate if we want this.

How will we measure success?

How many people use the "calm" emoji in their daily checkins.