Zap logger adds UUID to all logs in golang
php editor Xigua introduced: In golang, logging is an integral part of the development process. Zap logger is a very popular logging library that provides rich functions and high performance. Recently, a new feature has been added to Zap logger, which is to add UUID to all logs. The purpose of this function is to better track logs and facilitate developers to track problems in distributed systems. With this new feature, developers can more accurately locate problems and improve debugging efficiency. This is a very practical feature for engineers who develop using golang.
Question content
I used this method in lambda:
import ( "os" "go.uber.org/zap" "go.uber.org/zap/zapcore" ) func initlogger() *zap.logger { config := zap.newproductionencoderconfig() config.encodetime = zapcore.rfc3339timeencoder consoleencoder := zapcore.newjsonencoder(config) core := zapcore.newtee(zapcore.newcore(consoleencoder, zapcore.addsync(os.stdout), zapcore.infolevel)) return zap.new(core).with() }
In my lambda handler I have:
var ( log *zap.Logger ) func init() { log = u.InitLogger() } func handler(r events.APIGatewayProxyRequest) (*events.APIGatewayProxyResponse, error) { out, err := exec.Command("uuidgen").Output() uuid := strings.ReplaceAll(string(out), "\n", "") if err != nil { log.Error(err.Error()) } log.Info("PRINT_1", zap.Any("uuid", uuid), zap.Any("Request", r.Body)) }
I have a question, is it possible to add uuid to all logs without adding them one by one? Because in every log where I need to print something, I need to add zap.any("uuid", uuid)
The problem is that I need to pass the uuid as parameter to all methods to print it in log message or error.
Workaround
You will have to rearrange your code a bit since you are just creating the uuid in the handler which means it is request specific while the logger is global of...
However, the point for this library is that you have to create a sublogger (in fact, you're already doing this: you just pass the fields there). Any subsequent logs written to the sublogger will contain these fields.
For example:
func main() { logger := initlogger(zap.string("foo", "bar")) logger.info("first message with our `foo` key") logger.info("second message with our `foo` key") } func initlogger(fields ...zap.field) *zap.logger { config := zap.newproductionencoderconfig() config.encodetime = zapcore.rfc3339timeencoder consoleencoder := zapcore.newjsonencoder(config) core := zapcore.newtee(zapcore.newcore(consoleencoder, zapcore.addsync(os.stdout), zapcore.infolevel)) return zap.new(core).with(fields...) }
Output:
{"level":"info","ts":"2022-11-24T18:30:45+01:00","msg":"First message with our `foo` key","foo":"bar"} {"level":"info","ts":"2022-11-24T18:30:45+01:00","msg":"Second message with our `foo` key","foo":"bar"}
The above is the detailed content of Zap logger adds UUID to all logs in golang. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

This article explains Go's package import mechanisms: named imports (e.g., import "fmt") and blank imports (e.g., import _ "fmt"). Named imports make package contents accessible, while blank imports only execute t

This article explains Beego's NewFlash() function for inter-page data transfer in web applications. It focuses on using NewFlash() to display temporary messages (success, error, warning) between controllers, leveraging the session mechanism. Limita

This article details efficient conversion of MySQL query results into Go struct slices. It emphasizes using database/sql's Scan method for optimal performance, avoiding manual parsing. Best practices for struct field mapping using db tags and robus

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article details efficient file writing in Go, comparing os.WriteFile (suitable for small files) with os.OpenFile and buffered writes (optimal for large files). It emphasizes robust error handling, using defer, and checking for specific errors.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
