Skip to content

chore(logging): Structured logs and counters for submit events #58

@ArchILLtect

Description

@ArchILLtect

Problem / context

Need minimal visibility into usage and outcomes without full analytics.

Proposed solution

  • Log structured entries on submit: mode, challengeId, language, outcome, duration
  • Optional in-memory counters per mode

In scope / Out of scope

In scope:

  • Logging statements, small counter utility
    Out of scope:
  • Metrics endpoint/UI

Acceptance criteria

  • Logs include fields above
  • Basic counters tracked (if implemented)

Area

area:logging

Dependencies / related issues

Practice and Drill submit handlers

Checklist

  • I’ve checked existing issues for duplicates.
  • I can help implement this and open a PR.

Metadata

Metadata

Assignees

Labels

area:loggingLog4J configuration, structured logging, MDC, and log hygiene.choreMaintenance, refactors, and non-feature tasks (e.g., config, build, logging hygiene).priority:P1-highHigh importance; schedule next.project:mvpUse for all issues/PRs that belong to the MVP release. Will auto-add labeled items to the board.status:triageNewly filed or uncategorized. Needs initial review, labeling, and priority assignment.

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions