review log levels of some statements #248
Comments
tahini
added a commit
to tahini/trRouting
that referenced
this issue
Aug 7, 2023
Part of chairemobilite#248 The alternatives calculation statements are set to 'debug' instead of 'info'. The log statement at the beginning and end of the v2/* routes are set to 'info' and parameters are removed, spdlog will associate a timestamp with the log, so no need to display the application's time. If a catchall exception occurs, the log level is 'error'. TODO Cleanup the 'debug' statements and set a few as 'trace'
greenscientist
pushed a commit
that referenced
this issue
Aug 29, 2023
Part of #248 The alternatives calculation statements are set to 'debug' instead of 'info'. The log statement at the beginning and end of the v2/* routes are set to 'info' and parameters are removed, spdlog will associate a timestamp with the log, so no need to display the application's time. If a catchall exception occurs, the log level is 'error'. TODO Cleanup the 'debug' statements and set a few as 'trace'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When logging info, we have a lot of
calculating alternative x from a total of y ..., but nothing else.We should revisit our log statements to allow high level information in
infolevel, then increase for log statements fordebugandtrace.The text was updated successfully, but these errors were encountered: