timber 1.0.4 → 1.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 08cb61746c20295dafbfcf1a098664dd9a7ac0ce
-  data.tar.gz: f7a59dd084e99faac34169d37bc49f33a0aafba0
+  metadata.gz: 8e73e5010b44d99e5adfb9a250bc263acd7c0880
+  data.tar.gz: 6df96f28f4362e88098bc7b2db8085fbc45146ae
 SHA512:
-  metadata.gz: 40ffc77bceab9aec868f3f0592054970bd535abcdc6fda63101859605cd68a392faf2a7f7f13970cd6091370f2b711dc2f52072cede1f2d3aee760ef76274ba6
-  data.tar.gz: c2b7781da71ee771da0bb771295b83166f22446cf77bc27905d1a08311079b4b1a7ac3f43ca0011002148dff372f185c3180845905e8b8646960624278122759
+  metadata.gz: d156c42c78a02cf4f5627afb7ff70b1350e6f8abba7f984e1351f70fe7b54bdca3b421d02758575d5e5f287cd300e57c0e30c24a76d8fb70a975df71b683320c
+  data.tar.gz: bae815ef090ea535e10c7620d66293abb8c82ef9b134bfea3797fdfa3e66f590c5d991cbd817837deb767c6cd46a21fb90a0e3823ea7da0039c108af37e18150

data/README.md

@@ -12,49 +12,18 @@
 
 1. [What is timber?](#what-is-timber)
 2. [Why timber?](#why-timber)
-3. [How does it work?](#how-does-it-work)
 4. [Logging Custom Events](#logging-custom-events)
-5. [The Timber Console / Pricing](#the-timber-console-pricing)
+5. [The Timber Console / Pricing](#the-timber-console--pricing)
 6. [Install](#install)
 
 
 ## What is Timber?
 
-Glad you asked! :) Timber takes a different approach to logging, in that it automatically
-enriches and structures your logs without altering the essence of your original log messages.
-Giving you the best of both worlds: human readable logs *and* rich structured data.
+[Timber](http://timber.io) is a different kind of logging platform; it goes beyond traditional
+logging by automatically enriching your logs with application level metadata, turning them
+into rich, structured events without altering the essence of logging.
 
-And it does so with absolutely no lock-in or risk of code debt. It's just good ol' loggin'™!
-For example:
-
-1. The resulting log format, by deafult, is a simple, non-proprietary, JSON structure.
-2. The [`Timber::Logger`](lib/timber/events) class extends `Logger`, and will never change or
-   extend the public API.
-3. Where you send your logs is entirely up to you, but we hope you'll check out
-   [timber.io](https://timber.io). We've built a beautiful, modern, and *fast* console specifically
-   for the strutured data captured here.
-
-
-## Why Timber?
-
-Timber’s philosophy is that application insight should be open and owned by you. It should not
-require a myriad of services to accomplish. And there is no better vehicle than logging:
-
-1. The log is immutable and complete. [It is the truth](http://files.timber.io/images/log-is-the-truth.png) :)
-2. It’s a shared practice that has been around since the dawn of computers.
-3. It’s baked into every language, library, and framework. Even your own apps!
-4. The data is open, accessible, and entirely owned by you. Yay!
-
-The problem is that logs are unstructured, noisy, and hard to use. `grep` can only take you so
-far! Timber solves this by properly structuring your logs, making them easy to search and
-visualize -- enabling you to sanely realize the power of your logs.
-
-
-## How does it work?
-
-Timber automatically structures your logs by taking advantage of public APIs.
-
-For example, by subscribing to `ActiveSupport::Notifications`, Timber can automatically turn this:
+For example, it turns this:
 
 ```
 Completed 200 OK in 117ms (Views: 85.2ms | ActiveRecord: 25.3ms)
@@ -62,7 +31,7 @@ Completed 200 OK in 117ms (Views: 85.2ms | ActiveRecord: 25.3ms)
 
 Into this:
 
-```json
+```javascript
 {
   "dt": "2016-12-01T02:23:12.236543Z",
   "level": "info",
@@ -74,7 +43,7 @@ Into this:
       "remote_addr": "123.456.789.10",
       "request_id": "abcd1234"
     },
-    "user": {
+    "user": {  // <---- http://i.giphy.com/EldfH1VJdbrwY.gif
       "id": 2,
       "name": "Ben Johnson",
       "email": "ben@johnson.com"
@@ -89,8 +58,30 @@ Into this:
 }
 ```
 
-It does the same for `http requests`, `sql queries`, `exceptions`, `template renderings`,
-and any other event your framework logs. (for a full list see [`Timber::Events`](lib/timber/events))
+Notice we include data that isn't in the log message directly. It does the same for
+`http requests`, `sql queries`, `exceptions`, `template renderings`, and any other event
+your framework logs.
+
+(for a full list see [`Timber::Events`](lib/timber/events))
+
+
+## Why Timber?
+
+Glad you asked! :)
+
+1. It's application aware and enriches your logs with data you can't get otherwise. This
+   entire process is fully managed for you.
+2. It defines a shared schema across all of our libraries. Meaning your log data, across all
+   applications, will be normalized.
+3. It does not alter the original log message, giving you the best of both worlds: human
+   readable logs *and* rich structured events.
+4. It's completely transparent with absolutely no vendor lock-in or risk of code debt. Timber
+   adheres exactly to the `Logger` API. Meaning Timber can be installed and removed without
+   any reprocusion.
+
+What really makes Timber unique is that at the end of the day it's just good ol' loggin'.
+No special API, no proprietary data format, the data is accessible and owned by you.
+[Woo!](http://i.giphy.com/7JYWGKgwxga5i.gif)
 
 
 ## Logging Custom Events
@@ -122,6 +113,20 @@ No mention of Timber anywhere!
 
 ## The Timber Console / Pricing
 
+Like my mother always said:
+
+> What good is structured log data if you can't search and visualize it?
+
+Enter [the Timber Console](https://timber.io). It's a modern, fast, and beautiful console for
+searching and visualizing your logs.
+
+A few example queries:
+
+  1. `context.user.email:ben@johnson.com` - Tail a specific user!
+  2. `context.http.request_id:1234` - View *all* logs for a given HTTP request!
+  3. `event.http_reponse.time_ms>3000` - Easily find outliers and have the proper context to resolve them!
+  4. `level:warn` - Log levels in your logs. Imagine that!
+
 > This is all gravy, but wouldn't the extra data get expensive?
 
 If you opt use the [Timber Console](https://timber.io), we only charge for

data/lib/timber/log_devices/http.rb

@@ -8,7 +8,7 @@ module Timber
     #
     # See {#initialize} for options and more details.
     class HTTP
-      API_URI = URI.parse("https://api.timber.io/http_frames")
+      API_URI = URI.parse("https://logs.timber.io/frames")
       CONTENT_TYPE = "application/x-timber-msgpack-frame-1".freeze
       CONNECTION_HEADER = "keep-alive".freeze
       USER_AGENT = "Timber Ruby Gem/#{Timber::VERSION}".freeze

data/lib/timber/version.rb

@@ -1,3 +1,3 @@
 module Timber
-  VERSION = "1.0.4"
+  VERSION = "1.0.5"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: timber
 version: !ruby/object:Gem::Version
-  version: 1.0.4
+  version: 1.0.5
 platform: ruby
 authors:
 - Timber Technologies, Inc.
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-12-15 00:00:00.000000000 Z
+date: 2016-12-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: msgpack