search

osu-tournament-rating / otr-api

API powering osu! Tournament Rating
https://otr.stagec.xyz/
GNU General Public License v3.0
8 stars 5 forks source link

Have more useful logs in `DataWorkerService` #545

Open hburn7 opened 1 day ago

hburn7 commented 1 day ago

Currently, I have the following issues with the logs in the DataWorker:

  1. It's impossible to tell what is actually going on at a glance.
  2. The logs spam the console and are basically useless outside of a trace scenario.

I'd like to see the following changes:

  1. Tournament and match processing logs are changed to Debug severity.
  2. Game and GameScore processing logs are changed to Trace severity.
  3. (Info severity): A summary is reported after a tournament completes processing which contains the number of Matches, Games, and Scores grouped by verification status and rejection reason. Basically a full report per tournament.

Questions:

  1. Do we ever have a scenario where we want to re-process specific matches? If so, we should look into how we can have these logs show up in an informative way. If not, all match logs can be marked as Debug.
myssto commented 1 day ago
  1. (Info severity): A summary is reported after a tournament completes processing which contains the number of Matches, Games, and Scores grouped by verification status and rejection reason. Basically a full report per tournament.

Can you elaborate more on what you would like this to look like?