Go-GRPC-Auth-Microservice
zap
Go-GRPC-Auth-Microservice | zap | |
---|---|---|
1 | 51 | |
120 | 20,947 | |
- | 0.9% | |
0.0 | 8.1 | |
9 months ago | 8 days ago | |
Go | Go | |
- | MIT License |
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.
Go-GRPC-Auth-Microservice
-
Go gRPC Clean architecture microservice with Prometheus, Grafana monitoring and Jaeger opentracing β‘οΈ
Let's try to create closer to real world gRPC microservice with tracing and monitoring π: Source code u can find here Core tools used what will be used: π PostgreSQL as database Redis for sessions and caching Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus
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??
What are some alternatives?
opentelemetry-rust - The Rust OpenTelemetry implementation
logrus - Structured, pluggable logging for Go.
prometheus-redistimeseries-adapter - Prometheus remote storage adapter for RedisTimeSeries
zerolog - Zero Allocation JSON Logger
go-grpc-middleware - Golang gRPC Middlewares: interceptor chaining, auth, logging, retries and more.
slog
redis-traffic-stats - Live monitor & analyze Redis queries on your client
glog - Leveled execution logs for Go
csgo_exporter - A Prometheus exporter for Counter-Strike: Global Offensive.
go-log - a golang log lib supports level and multi handlers
blast - Blast is a full text search and indexing server, written in Go, built on top of Bleve.
log - Structured logging package for Go.