feat(taskworker): capture task exception context via TaskErrorCaptureHook

[s-starostin]

Summary

Add a sentry-side TaskErrorCaptureHook for taskworker that:

• captures task exceptions to Sentry with task metadata tags
• emits a structured single-line worker log suitable for ingestion by Vector
• returns a bounded TaskError envelope to taskbroker-client for broker-side logging

Dependencies

Depends on:

• getsentry/sentry-protosFix namespacing issue in web/views #215
• feat(taskbroker): propagate TaskError from worker and log failure context on broker taskbroker#607

This PR also requires a released taskbroker-client version that includes:

• error_hook
• worker-side propagation of TaskError

Changes

Worker hook

• add TaskErrorCaptureHook in src/sentry/taskworker/adapters.py
• log structured summary on task failure:
  • task_id
  • taskname
  • namespace
  • exception_type
  • exception_message
  • root_cause_type
  • root_cause_message
• omit raw traceback from stdout logs
• keep bounded traceback in returned TaskError

Runtime wiring

• wire TaskErrorCaptureHook() into TaskbrokerApp(...) in src/sentry/taskworker/runtime.py

Why

This makes task failures visible and searchable in three places at once:

• worker logs
• broker logs
• Sentry events

It also keeps worker stdout clean and parseable for log collectors.

Logging behavior

Expected worker log shape:

taskworker.task_failed task_id="..." taskname="..." namespace="..." exception_type="..." exception_message="..." root_cause_type="..." root_cause_message="..."

Tests

• envelope uses fully qualified exception type
• summary log contains task context and exception fields
• summary log contains root cause for chained exceptions
• raise ... from None respects suppressed context
• envelope still contains traceback
• hook does not raise if Sentry capture fails
• hook does not raise if envelope build fails
• hook tolerates missing task metadata fields

Local validation

Validated locally with a deliberately crashing task:

• worker emitted structured taskworker.task_failed
• broker emitted structured task reported failure
• task IDs matched across worker and broker
• exception type and message were preserved end-to-end

Follow-up

Once the companion taskbroker-client release is published, pyproject.toml should be bumped to that released version before merge.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fef5aa7. Configure here.}

[s-starostin]

Real-world motivation: without this change, investigating task failures can require manually reproducing the task on a worker just to see the actual exception.

With this the worker emits a structured single-line failure log and taskbroker receives/logs the exception context end-to-end.

Example structured worker log after the change:

[markstory]

Real-world motivation: without this change, investigating task failures can require manually reproducing the task on a worker just to see the actual exception.

The workers already capture sentry errors for failures.