timber 1.1.9 → 1.1.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: cbe987d8fbffcd959912acd47bdca88392cb6639
-  data.tar.gz: 80f5e3d9615a6a1d31f0bf29708a9f14b32f4698
+  metadata.gz: cf8ca0fa8a0c433dbcc8e9579f709251a505acb2
+  data.tar.gz: 0f68b1ff1a44242ae1ea2cbc0deafca22f13aa47
 SHA512:
-  metadata.gz: 46c5cf19a12a27e92a8891b340af164429e6983343cfcd2dfb013ebfc167dd714863874ece6350619a7c58a6253cf44059b8d903249ffb35419b5b3d6b027523
-  data.tar.gz: 4f8e29cef3c8337df09f6c05541a67f00f89312eedccc667c692bf0afb7d6d08b9578e361346a336e343c270f25403214f07c7f2ce226e3b2f1bdb6e3195b295
+  metadata.gz: 5619ca746b6f89d05befe196ef82dc5a501fa019386151299674e415aa2c861dc2c2832b82ee80ad697954a77d3cf24f91bbac86fd503c0e8450ed296cdc5018
+  data.tar.gz: 59930d73ce4d2adb12271558644d62857d1f6def99156b166233cb82217cfcccd9971317e29581cb3dcd4f227acb1c19ffb708c1781dceaf0a8e337d096fea90

data/README.md

@@ -84,12 +84,6 @@ No problem! You can easily install Timber following these steps:
 </p></details>
 
 
-
-
-
-
-
-
 ## Send your logs (choose one)
 
 <details><summary><strong>Heroku (log drains)</strong></summary><p>
@@ -103,7 +97,7 @@ The recommended strategy for Heroku is to setup a
 
 </p></details>
 
-<details><summary><strong>All other platforms (Network / HTTP)</strong></summary><p>
+<details><summary><strong>Or, all other platforms (Network / HTTP)</strong></summary><p>
 
 1. *Specify* the Timber Network logger backend in `config/environments/production.rb`:
 
@@ -113,7 +107,7 @@ The recommended strategy for Heroku is to setup a
   # config/environments/production.rb (or staging, etc)
 
   network_log_device = Timber::LogDevices::Network.new(ENV['TIMBER_LOGS_KEY'])
-  config.logger = Timber::Logger.new(network_log_device) # <-- Use network_log_device instead of STDOUT
+  config.logger = ActiveSupport::TaggedLogging.new(Timber::Logger.new(network_log_device))
   ```
 
 2. Obtain your Timber API :key: by **[adding your app in Timber](https://app.timber.io)**.
@@ -122,7 +116,7 @@ The recommended strategy for Heroku is to setup a
 
 </p></details>
 
-<details><summary><strong>Advanced setup (syslog, file tailing agent, etc)</strong></summary><p>
+<details><summary><strong>Or, advanced setup (syslog, file tailing agent, etc)</strong></summary><p>
 
 Checkout our [docs](https://timber.io/docs) for a comprehensive list of install instructions.
 
@@ -184,10 +178,9 @@ end
 
 </p></details>
 
-<details><summary><strong>Timings</strong></summary><p>
+<details><summary><strong>Timing events</strong></summary><p>
 
-Timings allow you to easily capture one-off timings in your code; a simple
-way to benchmark code execution:
+Timings provid a simple way to time code execution:
 
 ```ruby
 start = Time.now

data/lib/timber.rb

@@ -1,6 +1,7 @@
 # core classes
 require "json" # brings to_json to the core classes
 
+require "timber/overrides/logger_add"
 require "timber/overrides/rails_stdout_logging"
 
 # Base (must come first, order matters)

data/lib/timber/event.rb

@@ -17,5 +17,9 @@ module Timber
     def to_msgpack(*args)
       as_json.to_msgpack(*args)
     end
+
+    def to_s
+      message
+    end
   end
 end

data/lib/timber/version.rb

@@ -1,3 +1,3 @@
 module Timber
-  VERSION = "1.1.9"
+  VERSION = "1.1.10"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: timber
 version: !ruby/object:Gem::Version
-  version: 1.1.9
+  version: 1.1.10
 platform: ruby
 authors:
 - Timber Technologies, Inc.
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-02-24 00:00:00.000000000 Z
+date: 2017-02-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: msgpack