Take the &env from a macro, and tell whether we are expanding into cljs.

You are providing diagnostic information in a thorough manner with DEBUG. It’s long and contains more information than you’ll need when gg using the application. The DEBUG logging level is used to retrieve data that is required to debug, troubleshoot, or test an application. This guarantees that the application runs smoothly.

Like debug, but first argument is expected to be a map with usefull more detailed data.

Like debug, but focused on exceptions.

Like debug, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.

This ERROR indicates that something critical in your application has failed. This log level is used when a serious issue is preventing the application’s functionalities from functioning properly. The application will continue to run for the most part, but it will need to be handled at some point.

Like error, but first argument is expected to be a map with usefull more detailed data.

Like error, but focused on exceptions.

Like error, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.

FATAL indicates that the application is about to prevent a major problem or corruption. The FATAL level of logging indicates that the application’s situation is critical, such as when a critical function fails. If the application is unable to connect to the data store, for example, you can utilise the FATAL log level.

Like fatal, but first argument is expected to be a map with usefull more detailed data.

Like fatal, but focused on exceptions.

Like fatal, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.

INFO messages are similar to how applications normally behave. They describe what occurred. For example, if a specific service was stopped or started, or if something was added to the database. During normal operations, these entries are unimportant. The information written in the INFO log is usually useful, and you don’t have to do anything with it.

Like info, but first argument is expected to be a map with usefull more detailed data.

Like info, but focused on exceptions.

Like info, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.

Decides which strategy implementation to use for choosing the loggers.

Records all of the application’s behaviour details. Its purpose is primarily diagnostic, and it is more granular and finer than the DEBUG log level. When you need to know what happened in your application or the third-party libraries you’re using, utilise this log level. The TRACE log level can be used to query code parameters or analyse algorithm steps.

Like trace, but first argument is expected to be a map with usefull more detailed data.

Like trace, but focused on exceptions.

Like trace, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.

When an unexpected application issue has been identified, the WARN log level is used. This indicates that you are unsure if the issue will recur or not. At this time, you may not notice any negative effects on your application. This is frequently an issue that prevents some processes from operating. However, this does not necessarily imply that the application has been affected. The code should, in fact, continue to function normally. If the issue recurs, you should examine these warnings at some point.

Like warn, but first argument is expected to be a map with usefull more detailed data.

Like warn, but focused on exceptions.

Like warn, but uses clojure format function, so first argument is string to translate and rest is arguments to supply it with.