Alternatives
Products that do what Loglayer: A fluid logging interface for JavaScript loggers does
This has been in use on our production systems for around two years now at Switchboard (https://switchboard.app). The problem we had was that we were using two different logging libs for our frontend and backend at the time (specifically roarr, and bunyan), and the API for the logging libs were not compatible with each other. Loglayer was designed to wrap around popular JS logging libraries where you can swap out any underlying library without re-writing your log entries to adapt to the new library. One common example is using plain "console" as a starting integration, but later…
- 1
- 2LI
2011 · logio.org
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15IM
Hello I'm Jack, I was previously a Site Reliability Engineer and i've been working on monitro.dev which makes log monitoring simple for individuals or small teams. It allows you to easily forward any logs to multiple channels such as Slack, Discord & Telegram. The events are also viewable though the admin dashboard and are easily filterable. Currently there is only an NPM package with javascript / typescript support but i have plans to expand this to other languages such as Python, Rust etc. The package has many options, one of them is forwarding any uncaught exception and as an event…
2024 · monitro.dev
- 16
- 17
- 18
- 19RL
I've just released rust-loguru, a logging library for Rust that aims to combine intuitive API design (inspired by Go/Python's Loguru) with Rust's performance characteristics. Some highlights: - Consistently outperforms the standard log crate by 50-80% in benchmarks. - Multiple log levels and an extensible handler system -File rotation with better performance than log4rs and other alternatives - Error handling utilities and context helpers I built this because I wanted a logger that was both ergonomic to use and high-performance. The benchmarks comparing it to slog, log, and tracing are…
2025 · crates.io
- 20DT
A few years ago, my team moved from Java to Go. Working on Go projects, we came across a variety of logging frameworks with different APIs outputting messages in different formats. Go seemed to be lacking a logging abstraction like slf4j, which has been so invaluable to the Java ecosystem. Without that abstraction layer, the APIs for configuring logging vary wildly across projects, and libraries must either add a dependency on one of those frameworks or simply avoid structured logging altogether. Dazl is a logging abstraction layer that decouples the logging API from specific Go logging…
2023 · github.com
- 21WC
We developed a module for developers in small to mid-sized companies. It’s an open-source logger for Node.js with a built-in web dashboard to view, filter, and search your app logs.
2024 · github.com
- 22AV
We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…
2025 · github.com
- 23SJ
2015 · github.com
- 24LR
2024 · docs.rs
Ranked by how close each launch is in meaning, then by votes. Refine with a description →