zap
go-grpc-middleware
Our great sponsors
zap | go-grpc-middleware | |
---|---|---|
51 | 7 | |
20,947 | 6,043 | |
1.7% | 1.6% | |
8.1 | 7.3 | |
4 days ago | 19 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
go-grpc-middleware
-
Seeking advice on implementing a tinyurl-like service using Go and gRPC.
Hello, Those interviews are even crazy for internship. Anyway 1. Try to find a simple CRUD example online. You can check [this](https://tutorialedge.net/golang/go-grpc-beginners-tutorial/) 2. For logging you can check [go-grpc-middleware](https://github.com/grpc-ecosystem/go-grpc-middleware) 3. You can grpc-gateway in case they want some REST endpoints too 4. Use base62 to encode your url. So at least 2 columns in your table **shortenedUrl** and **url** 5. For such a project no need to use an ORM ( it's not advised anyway ). Implement 2 functions, one to insert into the db and the other one to read from the db. Remember to use transaction though 5. For unit tests go with the standard library and mock the 2 functions ( erroneous and valid cases )
-
Understanding gRPC Concepts, Use Cases & Best Practices
Supported middlewares by gRPC framework.
-
[Question] Suggested way to update a database row using gRPC/PostgreSQL (pgx) ?
I do some basic validation at the server layer using a GRPC interceptor.
-
gRPC best practices
Example auth middleware: https://github.com/grpc-ecosystem/go-grpc-middleware/blob/master/auth/examples_test.go
-
Go, RabbitMQ and gRPC Clean Architecture microservice 💫👋
And initialize our gRPC service, here i used gRPC Middleware repository for unary interceptors:
-
Go gRPC Clean architecture microservice with Prometheus, Grafana monitoring and Jaeger opentracing ⚡️
I found this is very good gRPC Middleware repository, but we easy can create our own, for example logger interceptor:
What are some alternatives?
logrus - Structured, pluggable logging for Go.
pgx - PostgreSQL driver and toolkit for Go
zerolog - Zero Allocation JSON Logger
Go-gRPC-RabbitMQ-microservice - Go gRPC RabbitMQ email microservice
slog
stdlog - Logging packages for Go
glog - Leveled execution logs for Go
pam - Go wrapper module for the Pluggable Authentication Modules (PAM) API
go-log - a golang log lib supports level and multi handlers
flipt - Enterprise-ready, GitOps enabled, CloudNative feature management solution
log - Structured logging package for Go.
redigo - Go client for Redis