search

lafkob / swe681_game

Our game for SWE 681.
0 stars 1 forks source link

Set up logging system #2

Closed lafkob closed 8 years ago

lafkob commented 8 years ago

Probably slf4j?

StormGull commented 8 years ago

Need to have two sets of records: the moves for every game played (only after the games are completed) and the win/loss records. Any player should be able to see these, but only if they've logged in.

StormGull commented 8 years ago

Note: Logging system is in place, but we still have to determine what we want to log and what log we want to keep that information in. We can configure it to roll over based on the size of the file or the date or both. What logs should we have? Maybe: -Debugging log - A place to capture exceptions so we can see them but they never get to the user? I think you started something like this. -Game audit log: Like what we have in the audit logs users can look at, but with both valid and invalid move messages. -Catch all Spring messages somewhere?

lafkob commented 8 years ago

I think we could dump the game controller logging into one log, and the rest into another? Putting it all in one also will simplify this quite a bit.

StormGull commented 8 years ago

Closing this since we have the logging system set up and opening an issue to do a final check to make sure we're logging everywhere we want to.