Description
Wrap each analytics cron job in a try/catch that logs failures with enough context to debug, and emits a analytics_job_failed event so it can be surfaced (e.g. to logs/alerting) if a rollup silently stops running.
Why this matters
A silently-failing nightly job would produce stale dashboard numbers with no obvious signal that anything is wrong.
Files to touch
backend/src/analytics/jobs
Acceptance Criteria
Notes
This issue is part of the new analytics module effort (tracking, aggregation,
and reporting on player/game activity). Please keep new code inside
backend/src/analytics/ following the same module/controller/service/provider
layout used by existing modules (e.g. progress, streak, quests).
Description
Wrap each analytics cron job in a try/catch that logs failures with enough context to debug, and emits a
analytics_job_failedevent so it can be surfaced (e.g. to logs/alerting) if a rollup silently stops running.Why this matters
A silently-failing nightly job would produce stale dashboard numbers with no obvious signal that anything is wrong.
Files to touch
backend/src/analytics/jobsAcceptance Criteria
Notes
This issue is part of the new
analyticsmodule effort (tracking, aggregation,and reporting on player/game activity). Please keep new code inside
backend/src/analytics/following the same module/controller/service/providerlayout used by existing modules (e.g.
progress,streak,quests).