I'm happy to announce ring.middleware.logger <https://github.com/pjlegato/ring.middleware.logger>, which logs details of each Ring request to a file, or to arbitrary functions you provide. The emphasis is on simplicity -- you can plug it in and go with sane out-of-the-box defaults, without any user configuration required.
You can find it at https://github.com/pjlegato/ring.middleware.logger and on Clojars. I've been using it in production for several years, and it has now stabilized to the point where I feel comfortable announcing it to a wider audience. That said, it should be considered beta quality software -- API changes are unlikely, but there may be bugs. Feature suggestions and especially pull requests are welcome! You might like to use r.m.logger with its companion project, https://github.com/pjlegato/ring.middleware.conditional -- this allows you to activate any middleware selectively, based on arbitrary runtime state. For example, combining it with ring.middleware.logger, you can log only requests that have certain URI paths, certain IP addresses, or log selectively based any other condition you like. Best, Paul Legato -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
