search

UMM-CSci-3601 / 3601-lab4-mongo

Software Design Lab 4 - MongoDB, Javalin, and Angular
MIT License
0 stars 0 forks source link

Should we add server side logging? #6

Open NicMcPhee opened 6 years ago

NicMcPhee commented 6 years ago

We could using Java logging tools to provide server side logging. This would allow students to (perhaps) better see/understand what's happening on the server side of their system. This is how "real professionals" would probably do it, but it's not clear to me if it would actually be helpful for the students.

Thoughts?

kklamberty commented 6 years ago

Would this really provide a log file or would it print things to the console? I don't know much about logging, but I think it would be great to learn more. Is there an example of what you're talking about that I could look at?

NicMcPhee commented 6 years ago

Logging tools can typically send logging output to a variety of sources depending on how you configure them, and usually you can do multiple things all at the same time. So you can configure your logger to send info scrolling by on the console, debug info to a file, and critical errors to some service that turns them into text messages to the team (if you have such a service set up).

There are a lot of Java logging tools, and I'm not really sure what is "recommended" these days. slf4j seems to be Widely Used and we're already pulling it in as a dependency for some reason (I think having to do with SparkJava). "Java logging basics" provides a pretty good overview of the main things, and lots more info on the left side-bar if you want to dig deeper.

In principle, I would definitely be all for doing more with logging. My experience, though, is that configuring loggers is a pain and often confuses people more than it's worth in the end.

NicMcPhee commented 6 years ago

We're not going to do this this semester (Spring, 2018); we might want to come back to it later for S19, though.