Skip to content
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.

Commit

Permalink
Emojis everywhere!!
Browse files Browse the repository at this point in the history
  • Loading branch information
binarylogic committed Feb 14, 2017
1 parent fe9938e commit a08600f
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

---

:point_right: **Timber is in beta testing, if interested in joining, please email us at
👉 **Timber is in beta testing, if interested in joining, please email us at
[beta@timber.io](mailto:beta@timber.io)**

---
Expand Down Expand Up @@ -43,13 +43,13 @@ blog post.
2. **Human readability.** Structuring your logs usually means they become unreadable. Timber
*augments* your logs with structured data. Meaning we do not alter the original log message.
And in the Timber console, you'll see the humany-friendly message. Click the line, and you'll
get access to all of the structured data in a slide out panel. :open_mouth:
get access to all of the structured data in a slide out panel. 😮
3. **Reliable downstream consumption.** All log events adhere to a
[normalized, shared, schema](https://github.com/timberio/log-event-json-schema) that follows
[semantic versioning](http://semver.org/) and goes through a [standard release process](https://github.com/timberio/log-event-json-schema/releases).
This means you can rely on the structure of your logs and interact consistently with them
across apps of any language: queries, graphs, alerts, and other downstream consumers. No
surprises, less breakage, more reliability, happier developers. :smile:
surprises, less breakage, more reliability, happier developers. 😊
4. **Zero risk of code debt or lock-in.** Logging is a standard that has been around since the dawn
of computers. It's built into every language, framework, and library. Timber adheres strictly
to the default `Logger` interface. There are no special APIs, and no need to pepper your app
Expand Down Expand Up @@ -275,7 +275,7 @@ config.logger = ActiveSupport::TaggedLogging.new(Timber::Logger.new(STDOUT))
The recommended strategy for Heroku is to setup a
[log drain](https://devcenter.heroku.com/articles/log-drains). To get your Timber log drain URL:

**--> [Add your app to Timber](https://app.timber.io)**
👉 **[Add your app to Timber](https://app.timber.io)**

---

Expand Down

0 comments on commit a08600f

Please sign in to comment.