2fee79e1f5
:discard marks jobs as "discarded", i.e. jobs which permanently failed
due to e.g. exhausting all retries or explicitly being discared due to a
fatal error.
:cancel marks jobs as "cancelled" which does not imply failure.
While neither method counts as a job "exception" in the set of
telemetries we currently export via Prometheus, the different state
is visible in the (not-exported) metadata of oban job telemetry.
We can use handlers of those events to build bespoke statistics.
Ideally we'd like to distinguish in the receiver worker between
"invalid" and "already present or delete of unknown" documents,
but this is cumbersome to get get right with a list of
free-form, human-readable descriptions oof the violated constraints.
For now, just count both as an fatal error.
# but that is cumbersome to get right with a list of string error descriptions
|
||
|---|---|---|
| .. | ||
| cron | ||
| attachments_cleanup_worker_test.exs | ||
| publisher_worker_test.exs | ||
| purge_expired_activity_test.exs | ||
| purge_expired_filter_test.exs | ||
| purge_expired_token_test.exs | ||
| receiver_worker_test.exs | ||
| remote_fetcher_worker_test.exs | ||
| scheduled_activity_worker_test.exs | ||