Associate Sentry reports with specific task

[matthew-white]

Right now, we wrap all task code in a Sentry scope of task (code here). However, as @alxndrsn writes, this "makes searching for errors with specific tasks harder". This issue is to update the task code such that Sentry can associate reports with the specific task that failed.

[matthew-white]

@alxndrsn, you suggested at #1789 (comment):

This could be improved by explicitly wrapping task code in a Sentry scope, and tagging with e.g. task:$taskName.

That sounds good to me. 👍 Would that be accomplished by changing op: 'task' in the code to:

op: `task:${name}`

Or would we add a second Sentry.startSpan() in addition to the one that's currently there?

One thing I'm wondering about is that we do seem to pass the task name to Sentry via name. Does name show up in Sentry? Is it searchable?

[matthew-white]

Does name show up in Sentry?

I do see run-analytics in several places in the Sentry report with tracing mentioned at #1789 (comment). I'm not sure that that's from name though.

[alxndrsn]

Would that be accomplished by changing op: 'task'
...
Or would we add a second Sentry.startSpan()

I think neither - scopes and spans seem to be unrelated. See comment at #1789 (comment).

For more info on scopes: https://docs.sentry.io/platforms/javascript/enriching-events/scopes/