Loki vs Zap: What are the differences?
What is Loki? Like Prometheus, but for logs (by the makers of Grafana). Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate, as it does not index the contents of the logs, but rather a set of labels for each log stream.
What is Zap? Blazing fast, structured, leveled logging in Go (by Uber). Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API.
Loki and Zap can be primarily classified as "Logging" tools.
Loki and Zap are both open source tools. It seems that Zap with 7.22K GitHub stars and 553 forks on GitHub has more adoption than Loki with 6.48K GitHub stars and 364 GitHub forks.