Reuse logging client in interceptor of Golang grpc server method
I am building a grpc server using go. Currently the server provides three methods:
- submit homework
- Cancel job
- Get job status
I'm using datadog to log some metrics such as request count, duration, etc. The submitjob method looks like this:
func (s *myserver) submitjob(ctx context.context, request *submitjobrequest) (*submitjobresponse, error) { s.dd_client.logrequestcount("submitjob") start_time := time.now() defer s.dd_client.logrequestduration("submitjob", time.since(start_time)) resp := somefunc() return resp, nil }
The logging code in these three different server methods is almost identical. So I want to know how to avoid this duplication.
I noticed that golang grpc has the concept of interceptor. Basically I can define an interceptor function and use it to do pre/post processing of server method calls.
Following the documentation, I wrote an interceptor as follows:
func unaryInterceptor(ctx context.Context, req interface{}, info *grpc.UnaryServerInfo, handler grpc.UnaryHandler, ) (interface{}, error) { dd_client := NewDatadogClient() defer dd_client.Close() dd_client.LogRequestCount(info.FullMethod) start_time := time.Now() resp, err := handler(ctx, req) dd_client.LogRequestDuration(info.FullMethod, time.Since(start_time)) return resp, err }
The problem is that every time the interceptor is called, it creates and destroys a new datadog client. I think this is unnecessary. But since unaryinterceptor is just a method and not a class, I don't see a way to create the datadog client once and reuse it later? Is there a way to meet my needs?
Correct answer
Yes, don't create it on the spot, but move it to another file/package, let's call it datadog.go
You need to declare it as a singleton, so it only has 1 pointer in all usages, like...
(I use the type "datadogtype" to refer to the data type returned by the function "newdatadogclient", please specify the package and version to give more precise sample code)
//your package code.... var dataDog DataDogType //access it through a wrapper, the wrapper will init the var the first time, //the remaining times it will be reused func GetDataDog()(*DataDogType) { if dataDog == nil { dataDog = NewDatadogClient() } return dataDog }
Now, depending on your use case, if you return it as a pointer and close it, you will close all uses of it, so return the pointer itself and omit the part that closes it, or return the value, so it is a copy of the original of
BTW, can you share what datadog version and specific package you are using?
The above is the detailed content of Reuse logging client in interceptor of Golang grpc server method. 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
