Do I need to log the request to the server?

Question

go

This may seem like a trivial question.
Does the Go server need to log the fact of the request?
If yes, then why?

Let's use Django as an example.
INFO "GET / HTTP/1.1" 200 6698
POST "POST /create/ HTTP/1.1" 200 6632

Answer 1

go is usually hidden behind a reverse proxy (like nginx). Nginx has an access log, so logging it on the service side is redundant.
And why is this needed - for incident investigations, for compiling statistics on logs. For example, the number of requests per day / hour / minute / second - see load bursts, distribution by response codes, popular URLs, user IPs to see botnets from China. Tons of applications.

Answer 2

As long as it doesn't break, it's not necessary.
And when they break it, or something stops working, you will think - what idiot turned off the logs.

Answer 3

In addition to fixing the request, you also need to write at least some informative data about the operation of the server (response time, some statuses of the response to the request). If there is a downlink or a base where they go for data, it is very desirable to fix the status of the connection or response.
It's just a good habit and the right habit. When you get into a serious company, where even before getting into the pre-prod service, they drive tests into the tail and mane, you will grab rays of goodness from QA or DevOps, or your application will simply be deployed.