[IMPROVEMENT] Unify logs with extra static info like module/method/function/line

[innobead]

Is your improvement request related to a feature? Please describe (👍 if you like this request)

Currently, in longhorn components' logs, there is no module, function, or line info to quickly identify the code. Usually, we will rely on the message to look up the potential code place. It's better to have logs with that info for troubleshooting purposes.

Describe the solution you'd like

Can leverage CallerPrettyfier to achieve the goal, and apply to all components and libraries.

package log
import (
 "fmt"
 "runtime"
 "strings"
"github.com/sirupsen/logrus"
)
func init() {
 logrus.SetReportCaller(true)
 formatter := &logrus.TextFormatter{
  TimestampFormat:        "02-01-2006 15:04:05", // the "time" field configuratiom
  FullTimestamp:          true, 
  DisableLevelTruncation: true, // log level field configuration
  CallerPrettyfier: func(f *runtime.Frame) (string, string) { 
   return "", fmt.Sprintf("%s:%d", formatFilePath(f.File), f.Line)
  },
 }
 logrus.SetFormatter(formatter)
}
func formatFilePath(path string) string {
 arr := strings.Split(path, "/")
 return arr[len(arr)-1]
}

Additional context

N/A

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

  • you can see there are two more fields in the log: func, file

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at

  • feat(log): add function name and line number in log message longhorn-manager#2231

[innobead]

@ChanYiLin let's apply this to all components.

[roger-ryao]

Verified on master-head 20231024

• longhorn master-head febfa7e
• longhorn-manager master-head longhorn/longhorn-manager@5e0868b

The test steps

#5509 (comment)

Result Passed

• We can see that there are two additional fields in the log: func, file