Member-only story
Server — side logging with Go
Even from Javascript frontend
- part: creating the service
- part: improving the service
- part: upgrade for web
- part: adding SSE
- part: simple javascript frontend functionality
- part: frontend — backend communication
- part: you are reading it right now
- part: run it all in docker
- part: adding database container
- part: database — service communication
Addition 1: functions, methods, pointers and interfaces
Addition 2: websocket communication
Addition 3: socket communication
Why to write your own logging?
There are ton of loggers in the Go world. Fast, easy, complicated, slow, … you name it.
The reason, why there are so manys is simple: everyone one of us is different and every one of us have different demands. So every one of us see logs as something specific for him, because I, You, Him, Her,… will be those one’s who will go through those logs in case something went wrong. And you want those logs to be the way you want. So it makes sense to make logging your personal thing.
But I advise you: try bunch of them.
Zap, Logrus, … , search and try. You can even use Go’s built — in log() functionality.
This article will show you, how — and why — you can built your own logging functionality. Functionality, that will act the same on Windows, Linux and MacOS and even when running in Docker.
Jump right in with creating log.go file
In the root of the project, create new file, called log.go. In that file create a new function called logInfo(), code below. This function does nothing more now, than prints some information to the console.
