Clojure: log to console when code is being executed in a go block or thread

Question

With many go blocks going at once, all writing to the console, the text can get jumbled/intermingled when it arrives at the console. How to avoid this, so trace output forms as correctly in the console as intended when it was emitted from within the go block?

send it to an agent who does the logging - If my theoretical knowledge is correct agents serialize their in-queu — birdspider
– birdspider, Commented Sep 22, 2015 at 11:44

Chris Murphy · Accepted Answer · 2015-09-22 14:05:05Z

3

This answer uses core.async itself. The following from a talk:

;;;;; Logging Handler ;;;;;

(def log-chan (chan))

(thread
 (loop []
   (when-let [v (<!! log-chan)]
     (println v)
     (recur)))
 (println "Log Closed"))


(close! log-chan)

(defn log [msg]
  (>!! log-chan msg))

(log "foo")

Code copied verbatim from here

Talk was by Timothy Balridge and is here

I have an atom for turning debugging on and off. To be precise about the messages that are displayed the usage is like this:

(u/log @debug (str "Asked " info-ele ", and got back: " some-return))

At the other end like this:

(defn log [debug msg] 
  (when debug (>!! log-chan msg)))

edited Sep 22, 2015 at 14:05

answered Sep 22, 2015 at 12:56

Chris Murphy

6,5092 gold badges27 silver badges46 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

erikprice Over a year ago

You could even alts! a separate channel instead of an atom for turning debugging on and off, and just make the on/off state a loop variable.

Community · Accepted Answer · 2017-05-23 12:23:50Z

1

Using a core.async channel to serialise all logging events will work, but a more standard way is to use a logging framework like logback or log4j. They are both designed for logging events from multiple threads (which is effectively what's happening when you're logging from inside a core.async go block).

Best practices for Java logging from multiple threads?

edited May 23, 2017 at 12:23

CommunityBot

11 silver badge

answered Sep 23, 2015 at 1:17

Daniel Compton

14.7k5 gold badges43 silver badges64 bronze badges

2 Comments

Chris Murphy Over a year ago

There have been lots of standard Java logging frameworks over the years. They all need to be configured, have the right jar file in the right place, have incompatibilities between them ironed out, source code changes done (sometimes to every file). Which is the most likely to be the standard in the future - logback or log4j?

Daniel Compton Over a year ago

Logback, although you'll use it through clojure.tools.logging "Logback is intended as a successor to the popular log4j project, picking up where log4j leaves off". My opinion on this is that it's worth taking the hour or so to learn a logging framework and it's config, as it will save you a lot of time in the long run. With slf4j and clojure.tools.logging, you can swap out the logging implementation and keep the same source.

Collectives™ on Stack Overflow

Clojure: log to console when code is being executed in a go block or thread

2 Answers 2

1 Comment

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related