client_golang
zap
client_golang | zap | |
---|---|---|
19 | 51 | |
5,139 | 20,981 | |
1.1% | 1.0% | |
8.7 | 8.1 | |
6 days ago | 9 days ago | |
Go | Go | |
Apache License 2.0 | 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.
client_golang
-
5 Ways to Improve Your API Reliability
Prometheus, an open-source systems monitoring and alerting toolkit, has client libraries that allow you to instrument your services in a variety of languages. Here's an example of how you might use the Go client library to expose metrics on an HTTP endpoint. We will leverage the prometheus go client to expose metrics and create them.
-
a tool for quickly creating web and microservice code
Monitoring prometheus, grafana
- The most helpful Go Packages
- Observabilidade com Prometheus
-
How do you monitor your Go apps?
I'd recommend github.com/victoriametrics/metrics for exporting custom metrics in Prometheus format. It is easier to use than the github.com/prometheus/client_golang.
-
prometheus exporter using Go
Start at the official documentation and the Go client library .
-
Any recommendation on Go Metrics libraries to report metrics to DataDog.
DataDog can read Prometheus metrics. Note that this approach works for metrics but not for traces although you can configure DataDog to receive OpenTelemetry traces as well https://github.com/prometheus/client_golang
-
How to observe an http web application in real time with pprof?
For Go, the standard is to use Prometheus and the Prometheus Go client library.
- High performance / low overhead metrics/instrumentation library?
- Collecting Go Runtime Metrics With OpenCensus
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?
twirp - A simple RPC framework with protobuf service definitions
logrus - Structured, pluggable logging for Go.
opa-scorecard
zerolog - Zero Allocation JSON Logger
helm-charts - Prometheus community Helm charts
slog
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
glog - Leveled execution logs for Go
chi - lightweight, idiomatic and composable router for building Go HTTP services
go-log - a golang log lib supports level and multi handlers
jaeger-client-go - ๐ This library is DEPRECATED!
log - Structured logging package for Go.