正在将标准库日志重定向到logrus线程安全

I am using logrus library for structured logging in my Go project.

I have configured my logrus as below:

// Global variable for logging
var gLog = &Logger{moduleName: ModuleName, logrus: logrus.New()}

type Logger struct {
    moduleName string
    logrus     *logrus.Logger
}

func SetupGlobalLogger(logPrefix string, logMode string) error {
    if logMode == "file" {
        logFilePath := fmt.Sprintf("var/%s.log", vite.Environment())

        file, err := os.OpenFile(logFilePath, logFileFlags, logFilePermission)
        if err != nil {
            return err
        }
        gLog.logrus.SetOutput(file)

        // redirect logs written using standard log library to same place as logrus
        log.SetOutput(gLog.logrus.Writer())

        log.Println(vite.MarkInfo, "redirect log to file:", logFilePath)
    }

    return nil
}

In this Go project, there are several places where standard log library statements like log.Println() are used.

I want to redirect those log messages to logrus.

For that I am using following statement in above code.

log.SetOutput(gLog.logrus.Writer())

My question is: Is this thread safe?

If one thread/go-routine is executing log.Println() while another executing gLog.logrus.Info() or something on logrus, will that be fine?

Is Logrus Thread-safe?

Yes:

Thread safety

By default, Logger is protected by a mutex for concurrent writes.

Except when it isn't.

Most of the non-thread-safe cases are bugs which will occur only in rare situations. Whether any of them matter to you depends, of course, on your use case.