mulog
μ/log is a micro-logging library that logs events and data, not words! (by BrunoBonacci)
spyscope
Trace-oriented debugging tools for Clojure (by dgrnbrg)
| mulog | spyscope | |
|---|---|---|
| 4 | 1 | |
| 471 | 578 | |
| - | - | |
| 4.6 | 0.0 | |
| about 1 month ago | over 4 years ago | |
| Clojure | Clojure | |
| Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
mulog
Posts with mentions or reviews of mulog.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-20.
-
Tracing: Structured Logging, but better in every way
There are logging libraries that include syntactically scoped timers, such as mulog (https://github.com/BrunoBonacci/mulog). While a great library, we preferred timbre (https://github.com/taoensso/timbre) and rolled our own logging timer macro that interoperates with it. More convenient to have such niceties in a Lisp of course.
- A History of Clojure (2020) [pdf]
- Logging verbosely into a ring buffer?
-
Debugging in Clojure
Assuming the crash doesn't cause the process to completely exit, you could indeed use `scope-capture` for this. This works well for local dev. In theory, you could use `sc.api/spy` in production code, and then attach a remote repl to diagnose any crashes. I wouldn't recommend this though, I think it would be best to use a good logging library like Mulog: https://github.com/BrunoBonacci/mulog
spyscope
Posts with mentions or reviews of spyscope.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-07-06.
-
Debugging in Clojure
The first example about spyscope is.. not good. The point of it is you can stick it in front of any form, not to use it with println debugging. For a better example, at https://github.com/dgrnbrg/spyscope#spyp
What are some alternatives?
When comparing mulog and spyscope you can also consider the following projects:
timbre - Pure Clojure/Script logging library
debug-repl - A Clojure debug repl as nrepl middleware
re-frame-10x - A debugging dashboard for re-frame. X-ray vision as tooling.
cider - The Clojure Interactive Development Environment that Rocks for Emacs
clj-otel - An idiomatic Clojure API for adding telemetry to your libraries and applications using OpenTelemetry.
re-frame-flow - Graph based visualization tool for re-frame event chains
tick - Time as a value.
Riemann - A network event stream processing system, in Clojure.
blacklite - "Fast as internal ring buffer" Logback/Log4J2 appender using SQLite with zstandard dictionary compression and rollover.
logstash-logback-encoder - Logback JSON encoder and appenders