README.md in timberio-1.0.2 vs README.md in timberio-1.0.3
- old
+ new
@@ -1,28 +1,27 @@
# Timber
<p align="center" style="background: #140f2a;">
-<a href="http://github.com/timberio/timber-ruby"><img src="http://files.timber.io/images/ruby-library-readme-header.gif" height="370" /></a>
+<a href="http://github.com/timberio/timber-ruby"><img src="http://files.timber.io/images/ruby-library-readme-header.gif" height="469" /></a>
</p>
[](https://circleci.com/gh/timberio/timber-ruby/tree/master)
[](https://coveralls.io/github/timberio/timber-ruby?branch=master)
[](https://codeclimate.com/github/timberio/timber-ruby)
[](http://www.rubydoc.info/github/timberio/timber-ruby)
1. [What is timber?](#what-is-timber)
-2. [Examples](#examples)
-3. [Pricing](#pricing)
+2. [Logger Examples](#logger-examples)
+3. [Console Pricing](#console-pricing)
2. [Install](#install)
## What is Timber?
-Glad you asked :) Timber tames the crazy world that is logging. First, it *automatically*
-augments your logs with structured data. Second, it provides a transparent, no lock-in, API
-for logging your own events. Lastly, it can be paired with a [simple modern console](https://timber.io) for querying.
+Glad you asked! :) Timber turns your messy string logs into structured events with context where
+it can optionally be paired with our [simple modern console](https://timber.io) for querying.
For example, it automatically turns this:
```
Completed 200 OK in 117ms (Views: 85.2ms | ActiveRecord: 25.3ms)
@@ -67,11 +66,11 @@
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!
-## Examples
+## Logger Examples
> Another service? More lock-in? More code debt? More sadness? :*(
Nope! This is exactly why we created Timber. Timber is Just Logging™. No special API, no risk
of code debt, no weird proprietary data format locked away in our servers. Absolutely no lock-in!
@@ -126,29 +125,29 @@
just logging touching your code
*and* backfill them!
```
-## Pricing
+## Console Pricing
> This is all gravy, but wouldn't it get expensive?
If you opt to send your data to the [Timber service](https://timber.io), we only charge for
the size of the `message`, `dt`, and `event.custom` attributes. Everything else is
stored at no cost to you. [Say wha?!](http://i.giphy.com/l0HlL2vlfpWI0meJi.gif). This ensures
-pricing remains predictable. And our pricing is simple, we charge per GB transferred to us and
-retained, no user limits, and no weird feature matrixes. Lastly, the data is yours, in a simple
-non-proprietary JSON format.
+pricing remains predictable and simple. We charge per GB transferred to us and
+retained, no user limits, and no weird feature matrixes. Finally, the data is yours, in a simple
+non-proprietary JSON format that you can export to S3, Redshift, or any of our other integrations.
-For more details checkout our [timber.io](https://timber.io).
+For more details checkout out [timber.io](https://timber.io).
## Install
### 1. Install the gem:
```ruby
# Gemfile
-gem 'timberio', require: "timber"
+gem 'timberio'
```
### 2. Install the logger:
#### Heroku: