aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
authorsshaw <skye.shaw@gmail.com>2015-03-06 22:15:36 -0500
committersshaw <skye.shaw@gmail.com>2015-03-06 22:20:22 -0500
commitf9369c0f51e8c404dd12024037a055594bf0ace2 (patch)
tree9262099ef1dff89a2c2b61fc3efea4d7db308e9a /guides/source
parent387e7be458338db110f8a1ceeaf5952b39133a08 (diff)
downloadrails-f9369c0f51e8c404dd12024037a055594bf0ace2.tar.gz
rails-f9369c0f51e8c404dd12024037a055594bf0ace2.tar.bz2
rails-f9369c0f51e8c404dd12024037a055594bf0ace2.zip
More docs on tagged logging [ci skip]
Mention that tags can also come from a Proc that accepts the request object or something's to_s method
Diffstat (limited to 'guides/source')
-rw-r--r--guides/source/configuring.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/configuring.md b/guides/source/configuring.md
index 4ebd634cd6..b791114ed9 100644
--- a/guides/source/configuring.md
+++ b/guides/source/configuring.md
@@ -114,7 +114,7 @@ numbers. New applications filter out passwords by adding the following `config.f
defaults to `:debug` for all environments. The available log levels are: `:debug`,
`:info`, `:warn`, `:error`, `:fatal`, and `:unknown`.
-* `config.log_tags` accepts a list of methods that the `request` object responds to. This makes it easy to tag log lines with debug information like subdomain and request id - both very helpful in debugging multi-user production applications.
+* `config.log_tags` accepts a list of: methods that the `request` object responds to, a `Proc` that accepts the `request` object, or something that responds to `to_s`. This makes it easy to tag log lines with debug information like subdomain and request id - both very helpful in debugging multi-user production applications.
* `config.logger` accepts a logger conforming to the interface of Log4r or the default Ruby `Logger` class. Defaults to an instance of `ActiveSupport::Logger`.