chili_logger 0.0.5 → 0.0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0baddcb177c1e5a6676aa3a60040e37b17397958348944ff4f0b980b4c37bef2
-  data.tar.gz: 8511fd8734a086ec0b8fd82dea6329aa8e4bd351f6daa0405fa519d29b401c2c
+  metadata.gz: bcee860ae763961cedf6bd91456a7932a00ca2eae59f276380c2a90dd9479e12
+  data.tar.gz: cb5e2cc3075bbda8cba9baa7f29ae05f5f35b79eb3f7a986bc382dcba7052f03
 SHA512:
-  metadata.gz: 90f1f25ebd08ea66819dd74b86d05a073de1d317b7df3428e4bcda6ecfd5f94f7db5d907acbeed7a2ba5b7555a50e07e9a2d12d1a1217ab0571a4b03f8012318
-  data.tar.gz: 9319b3f0ffb1daf8800615873068bd96a4502424452009ca4a3683c776a3a4cd7231ff162c7bb68ec563898202436062d0cea0da3c4a9361db432a3b260e9527
+  metadata.gz: 2492803a054170942b232fd1186827ed1b4f635b6a5fc7de7883321be454756b841502afe744112e11b398fd1b27eaf4813fc5d10db12018e22e81d7534da443
+  data.tar.gz: f9e3ebd7f7414863fa78ab5affac2b9940fcd40a07a85489afdb3782869d1ce098d373ac861cdb4eed7259aa4b0575331a2f2bdae024953068d0cc9344e835cb

data/.byebug_history

@@ -1,4 +1,82 @@
 continue
+options
+continue
+options
+continue
+@desc_uniformizer.desc([])
+@desc_uniformizer.desc(options[:desc])
+@desc_uniformizer.desc
+@desc_uniformizer.desc(options[:desc])
+options
+continue
+options
+continue
+main_content.merge(uniformized_content)
+main_content
+continue
+main_content
+uniformized_content
+continue
+desc
+continue
+uniformized_content
+continue
+uniformized_content
+quit
+val.first.is_a?(Hash)
+val.first.is_a?(Hash) ? {} : record
+modified_record(val.first)
+val
+uniformized_val
+quit
+continue
+error.inspect.is_a?(String)
+error.inspect
+error.class.ancestors.include?(Exception)
+error
+new_error
+errors
+all_errors
+continue
+new_error.is_a?(String)
+continue
+new_error.is_a?(String)
+new_error.class
+new_error
+continue
+new_error
+continue
+new_error
+continue
+error
+new_error
+quit
+main_content[:errors] ||= @default.log_errors
+errors
+continue
+user[:cognito_id]
+new_user[:cognito_id]
+continuenew_user[:cognito_id]
+continue
+new_user
+continue
+user
+Thread.current[:current_log_user]
+Thread.current[:current_log_user] ||= default_user
+continue
+Thread.current[:current_log_user] ||= default_user
+continue
+Thread.current[:current_log_user] ||= default_user
+continue
+Thread.current[:current_log_user] ||= default_user
+user
+continue
+log_user
+continue
+Thread.current[:current_log_user] ||= default_user
+Thread.current[:current_log_user]
+user
+continue
 e.class
 e.is_a?(Bunny:TCPConnectionFailed)
 e

data/Gemfile

@@ -12,3 +12,5 @@ gem 'rspec', '~> 3.0'
 gem 'rubocop', '~> 0.60.0', require: false
 
 gem 'httparty', '~> 0.18.1'
+
+gem "simplecov", "~> 0.17.1"

data/Gemfile.lock

@@ -1,8 +1,8 @@
 PATH
   remote: .
   specs:
-    chili_logger (0.0.5)
-      aws-sdk
+    chili_logger (0.0.9.1)
+      aws-sdk (~> 2.9, >= 2.9.0)
       bunny
       httparty
 
@@ -38,6 +38,7 @@ GEM
     byebug (11.0.1)
     concurrent-ruby (1.1.6)
     diff-lcs (1.4.2)
+    docile (1.3.2)
     httparty (0.18.1)
       mime-types (~> 3.0)
       multi_xml (>= 0.5.2)
@@ -45,6 +46,7 @@ GEM
       concurrent-ruby (~> 1.0)
     jaro_winkler (1.5.4)
     jmespath (1.4.0)
+    json (2.3.1)
     mime-types (3.3.1)
       mime-types-data (~> 3.2015)
     mime-types-data (3.2020.0512)
@@ -78,6 +80,11 @@ GEM
       ruby-progressbar (~> 1.7)
       unicode-display_width (~> 1.4.0)
     ruby-progressbar (1.10.1)
+    simplecov (0.17.1)
+      docile (~> 1.1)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.2)
     thread_safe (0.3.6)
     tzinfo (1.2.7)
       thread_safe (~> 0.1)
@@ -96,6 +103,7 @@ DEPENDENCIES
   rake (~> 12.0)
   rspec (~> 3.0)
   rubocop (~> 0.60.0)
+  simplecov (~> 0.17.1)
 
 BUNDLED WITH
    1.17.3

data/README.md

@@ -1,27 +1,271 @@
 # ChiliLogger
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/chili_logger`. To experiment with that code, run `bin/console` for an interactive prompt.
+ChiliLogger is a gem developed by Chiligum Creatives for internal use. It is used to monitor our ruby applications and generate logs with some uniformization.
 
-TODO: Delete this and the text above, and describe your gem
+## Table of Contents
+* [READ BEFORE CONTRIBUTING](##read-before-contributing)
+* [How it Works](##how-it-works)
+  * [Overview](###overview)
+  * [Anatomy of a Chiligum Log](###anatomy-of-a-chiligum-log)
+    * [Example Log](####example-log)
+    * [Environment](####environment)
+    * [Layer](####layer)
+    * [Type](####type)
+    * [Service](####service)
+    * [Action](####action)
+    * [Description](####description)
+    * [User](####user)
+    * [Main Content](####main-content)
+    * [Ops Metadata](####ops-metadata)
+    * [Timestamp](####timestamp)
+  * [A Primer on RabbitMQ and ElasticSearch](###a-primer-on-rabbitmq-and-elasticsearch)
+    * [RabbitMQ](####rabbitmq)
+    * [ElasticSearch](####elasticsearch)
+    * [Putting It All Together](####putting-it-all-together)
+* [Installation](##installation)
+* [Basic Usage](##basic-usage)
+  * [publish_instant_log params](####publish_instant_log-params)
+  * [publish_instant_log usage example](####publish_instant_log-usage-example)
+  * [publish_instant_log default argument values](####publish_instant_log-default-argument-values)
+  * [ChiliLogger's Singleton pattern](####ChiliLoggers-singleton-pattern)
+* [Advanced Usage](##advanced-usage)
+  * [Code Example](####advanced-code-example)
+  * [Error Logging](####error-logging)
+  * [Customizing a Started Log](####customizing-a-started-log)
+    * [Accessing the current_log](####accessing-the-current_log)
+    * [user](####user)
+    * [update_user](####update_user)
+    * [desc](####desc)
+    * [update_type](####update_type)
+    * [update_service](####update_service)
+    * [update_action](####update_action)
+    * [update_desc](####update_desc)
+    * [main_content](####main_content)
+    * [update_main_content](####update_main_content)
+    * [add_to_main_content](####add_to_main_content)
+    * [modified_records](####modified_records)
+    * [update_modified_records](####update_modified_records)
+    * [add_modified_record](####add_modified_record)
+    * [clear_log_info](####clear_log_info)
+* [Snippets For Quicker Logging](##snippets-for-quicker-logging)
+  * [Papertrail Optional Use](###papertrail-optional-use)
+  * [Logging Transactions in HTP Requests](###logging-transactions-in-http-requests)
+    * [Controllers](####controllers-logging-logic)
+    * [Models](####models-logging-logic)
+  * [Logging Rake Tasks](###logging-rake-tasks)
+    * [Logging Uncaught task Errors](####logging-uncaught-task-errors)
+    * [Logging Transactions in Tasks](####logging-transactions-in-tasks)
+    * [Logging Heartbeats in Tasks](####logging-heartbeats-in-tasks)
+* [Coverage](##Coverage)
 
-## Installation
+## READ BEFORE CONTRIBUTING
+The main thing you need to know before changing Chililogger's source code is this: we send our logs in JSON format and [Logstash parses and converts them to Elasticsearch objects](####elasticsearch), requiring all fields to have consistent primitive types. So suppose you send these logs: 
+```json
+// first log
+{
+  "user": {
+    "name": "Joe Doe"
+  }
+}
 
-Add this line to your application's Gemfile:
+// second log
+{
+  "user": "Mary Jane"
+}
+
+// third log
+{
+  "user": {
+    "name": {
+      "first": "Francis",
+      "last": "Coppola"
+    }
+  }
+}
+
+// fourth log
+{
+  "client": {
+    "name": "Angela"
+  }
+}
+```
+After receiving the first log, `Logstash` will parse it and define that the `user` field is always an object and that it **may** have a field called `name`, which is a string. Notice that it is not mandatory for logs to have a `user` and a `user.name`. But, if a log does have these fields, then they **must** be an object and a string, respectively.
+
+When Logstash receives the second log, it will see an inconsistency, because this time `user` is a string, not an object. Because of that, Logstash will ignore this log - in other words, **this log will not be saved to Elasticsearch**. When the third log arrives, the same will happen. It will see that `user` is consistent with what it expected, but that the field `user.name` is now an object, intead of being a string as was expected. This log will also be ignored by Logstash. The fourth log would be accepted though, since `client.name` hasn't been set yet.
+
+So if you are going to change anything in ChiliLogger, you have to keep this in mind: **the primitive types of fields in an Elasticsearch index must always be consistent**. If your changes generate logs with fields that already existed in the Elasticsearch index, but now have a different primitive type, Logstash will ignore these logs. This is important because Logstash just ignores incorrect logs without raising errors - so it may take a long time before the problem is noticed. If you need to change the type of a previously set field, you will need to create a new index/Logstash and make sure the logs are sent to this new Logstash.
+
+## How it works
+
+### Overview
+
+![ChiliLogger usual Flow](assets/images/chili-logger-flow.png)
+
+For the time being, only `RabbitMQ` is supported as the main message broker. Only `AWS SQS` is available as a fallback broker.
+
+If both the main message broker and the fallback message broker are down, ChiliLogger wil discard the log to keep the application running without raising any error. That's because raising errors would make the app crash and make it impossible to be used while the brokers are down.
+
+
+### Anatomy of a Chiligum Log
+
+The ChiliLogger gem was created to guarantee some level of uniformization in logs generated by all our ruby applications. So, to better understand its functioning and usage, it is helpful to first understand what kind of logs it is trying to generate. An example log would look like the following:
 
+#### Example Log
+```json
+{
+  "env": "development",
+  "layer": "creatives",
+  "type": "transaction",
+  "service": "videos",
+  "action": "create",
+  "desc": "development.creatives.transaction.videos.create",
+  "user": { 
+    "cognito_id": "88", 
+    "email": 'exemple@test.com',
+    "company_cognito_id": "75",
+    "company_name": "Chiligum Creatives",
+    "ghost_user_cognito_id": "not_specified"
+  },
+  "transaction": {
+    "modified_records": { 
+      "videos": [{ "id": 42, "title": 'Lateralus' }],
+      "gallery_tags": [{ "id": 50 }, { "id": 51 }, { "id": 52 }],
+      "tags": [{ "id": 23, "name": "tool" }]
+    },
+    "errors": [],
+    "backtrace": [
+      "app/views/dashboard/controllers/videos_controller.rb:17 in block 'create'"
+    ],
+  },
+  "ops_metadata": {
+    "server_url": "https://app.chiligumvideos.com"
+  },
+  "timestamp": "2020-06-30T18:08:59-03:00"
+}
+
+```
+Below is a short explanation of each one of the log attributes.
+
+#### Environment
+The `env` attribute is used for tagging the log and tells in which environment the app was running when the log was created. We are mainly concerned with three possible environments: `production`, `staging`, and `development`. Needless to say, logs from a production environment are the most important to us, but staging and development logs can be useful for debugging/testing.
+
+---
+
+#### Layer
+The `layer` attribute is also used for tagging and tells us in which layer of the Chiligum platform the log was created. Usually, the layer will correspond to the name of the application/service where ChiliLogger was installed. For instance, it could be 'creatives', 'api', 'render', etc...
+
+---
+
+#### Type
+Also a tagging attribute, tells what type of log it is. Chiligum has 3 main types of logs: 
+  - `transaction` is used for logging transactions made by users, such as creating a campaign, uploading a file to the gallery, etc...
+  - `uncaught_error` is used for logging internal server errors and to help us find problematic points in our applications;
+  - `monitoring` is used to monitor the health of our servers, providing information such as CPU usage, uptime, etc...
+
+ChiliLogger is concerned only with `transaction` and `uncaught_errors`, since they are the only ones that can be generated in the application itself. Monitoring logs are created by other monitoring services, like ElasticSearch Beats or AWS Cloudwatch.
+
+---
+
+#### Service
+The `service` tagging attribute is used to tell what group of features the user was trying to interact with. Services can be things like 'videos', 'campaigns', 'banners', 'gallery' and will usually have the similar names to the Controllers in an application.
+
+---
+
+#### Action
+The `action` tagging attribute describes what action exactly the user was trying to perform in our platform. Usual values for it are 'create', 'update, and 'delete'. Usually, action tags will have similar names to Controllers' methods.
+
+---
+
+#### Description
+The `desc` is the last of the tagging attributes and is used to combine all of the previous attributes in a single tag, allowing any person that is examining a log to quickly identify what the log is about. It is structured in the following manner:
 ```ruby
-gem 'chili_logger'
+"#{env}.#{layer}.#{type}.#{service}.#{action}"
 ```
+Notice that the tags are separated by a `.` period. That's because the `desc` tag is also used to create the [routing_key for topic exchanges](https://www.rabbitmq.com/tutorials/amqp-concepts.html#exchange-topic) when ChiliLogger is using RabbitMQ as its MessageBroker.
 
-And then execute:
+---
 
-    $ bundle install
+#### User
+The `user` stores the main infos about the user whose request generated the log. The user is an object that accepts five attributes: 
+  - `cognito_id`, the user's global ID, the one the identifies it in Cognito's DB;
+  - `email`, so we can easily know who the user is;
+  - `company_cognito_id`, the global ID of the user's company;
+  - `company_name`;
+  - `ghost_user_cognito_id`, for cases when admin users can log as other users. In these cases, the admin's global ID should be stored in the ghost_user_cognito_id;
+
+---
+
+#### Main Content 
+##### (Transaction | Error)
+The `main_content` will have all other data relevant to the log. The main content of a log will be stored in a key with the same name as the log `type`. So a transaction log, as in the example above, willhave its main_content stored in the `transaction` field. In an error log, it would be in an `error` field.
+It is an object with that accepts the folowwing attributes:
+  - `modified_records`, listing all tables modified and the records themselves;
+  - `errors`, listing errors found during the transaction and will usually be an empty array if the transaction was successful;
+  - `backtrace`, automatically created by the gem itself and showing the backtrace of the transaction and its processing;
+
+---
+
+#### Ops Metadata
+Based on the configuration data(`:server_url`, `:cloud_provider`) that is passed to ChiliLogger when it is initialized, the log will also have metadata about the server itself where the application is running.
+
+---
+
+#### Timestamp
+ChiliLogger automatically adds a `timestamp` to the log.
+
+### A Primer on RabbitMQ and ElasticSearch
+Since Chiligum's logging system is entirely based on RabbitMQ and ElasticSearch, it's useful to have at least a high level understanding of how they work and how they are being used together.
+
+#### RabbitMQ
+RabbitMQis a popular message broker that can handle a high traffic of messages. Its role in our logging system is to simply receive all incoming logs and put them in appropriate queues, so other services can have access to these logs and process and/or store them in a central database.
+
+RabbitMQ has 4 main entities: 
+  * `publishers`, which create the messages (in our case, it's ChiliLogger creating the logs);
+  * `exchanges`, where publishers send the messages to;
+  * `queues`, which receive just the messages from the exchange that are relevant to them.
+  * `consumers`, which get messages from specific queues (in our case, that's Logstash/Elasticsearch)
+
+![explanation for RabbitMQ basic functioning](assets/images/rabbit-basic-functioning.png)
+
+All messages are published to an exchange with a `routing_key`, which allows the exchange to know which queues should receive that message. RabbitMQ has a couple of possible exchange types and each one of them has a different way of distributing the messages among the queues. At Chiligum, we use only the `topic` type, the most flexible one and the one that can simulate all other types if needed. 
+
+In topic exchanges, the routing_key will be composed of keywords separated by dots ("."). Queues, on the other hand, will define which keywords they are interested at by defining their `binding_keys`. So a message with `production.creatives.videos` as routing_key would bedelivered to any queue with a matching binding_key of `production.creatives.videos`. Queues can use wildcards(`*`, `#`) in their binding keys. It's easier to understand it with the exemple from the RabbitMQ tutorials itself:
+
+> `*` can substitute for exactly one word. `#` can substitute for zero or more words.
+>
+> In this example, we're going to send messages which all describe animals. The messages will be sent with a routing key that consists of three words (two dots). The first word in the routing key will describe a celerity, second a colour and third a species: "`<celerity>.<colour>.<species>`".
+
+![explanation for RabbitMQ topic excahnges](assets/images/rabbit-topic-explanation.webp)
+>
+> We created three bindings: Q1 is bound with binding key "`*.orange.*`" and Q2 with "`*.*.rabbit`" and "`lazy.#`". These bindings can be summarised as:
+>
+> Q1 is interested in all the orange animals. Q2 wants to hear everything about rabbits, and everything about lazy animals.
+>
+> A message with a routing key set to "`quick.orange.rabbit`" will be delivered to both queues. Message "`lazy.orange.elephant`" also will go to both of them. On the other hand "quick.orange.fox" will only go to the first queue, and "`lazy.brown.fox`" only to the second. "`lazy.pink.rabbit`" will be delivered to the second queue only once, even though it matches two bindings. "`quick.brown.fox`" doesn't match any binding so it will be discarded.
+
+
+
+#### ElasticSearch
+ElasticSearch is part of the so-called Elastic Stack. It is an open source database that offers powerful, fast querying of data. It is usually used with Logstash, also a tool of the Elastic Stack. Logstash can fetch or receive data from many different sources and can parse this data so it is in compliance with ElasticSearch data structures. At Chiligum, we create logs in JSON format and it is Logstash who converts it to Elasticsearch objects. Logstash can also work with RabbitMQ, creating queues and receiving data form them.  
 
-Or install it yourself as:
+#### Putting It All Together
+By now, perhaps it has already become clear how RabbitMQ and ElasticSearch are being used for Chiligum's logging system. `ChiliLogger` will create logs and publish them to a topic exchange in `RabbitMQ` with the appropriate routing_keys. RabbitMQ will distribute these logs to the queues created by `Logstash` instances. The distribution of messages will be according to the queues' binding_keys. Logstash instances will keep polling the queues, fetching messages, parsing them to Elasticsearch objects and storing them in `Elasticsearch indexes`. An Elasticsearch index is analogous to a SQS table, it's basically a collection of stored data.
 
-    $ gem install chili_logger
+![video showing Chiligum's logging system in action](assets/images/chiligum-logging-system.gif)
 
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'chili_logger'
+```
+
+#### Basic Initialization
+
+Create a initializer file and configure ChiliLogger passing all the relevant information. It is recommended to deactivate ChiliLogger when running tests:
 
-Create a initializer file and configure ChiliLogger passing all the relevant informations:
 ```ruby
 # config/initializers/chili_logger.rb 
 require 'chili_logger'
@@ -30,21 +274,20 @@ is_deactivated = Rails.env.test?
 
 ChiliLogger.instance.config({
   deactivated: is_deactivated,
-  log_env: 'development',
-  log_layer: 'creatives',
-  server_url: ENV['SERVER_URL'],
-  cloud_provider: ENV['CLOUD_PROVIDER'],
-  msg_broker_name: :rabbitmq,
+  log_env: Rails.env, # sets the log's env attribute
+  log_layer: ENV['APPLICATION_NAME'], # sets the log's layer attribute
+  server_url: ENV['SERVER_URL'], # used for log's ops_metadata attribute
+  cloud_provider: ENV['CLOUD_PROVIDER'], # used for log's ops_metadata attribute
+  msg_broker_name: :rabbitmq, # ChiliLogger's Message Broker
   msg_broker_config: {
     user: ENV['RABBIT_USER'],
     password: ENV['RABBIT_PASSWORD'],
     ip: ENV['RABBIT_IP'],
     port: ENV['RABBIT_PORT'],
     exchange_name: ENV['RABBIT_EXCHANGE'],
-    routing_key: ENV['RABBIT_ROUTING_KEY']
   },
-  error_handler: :aws_sqs,
-  error_handler_config: {
+  fallback_broker: :aws_sqs, # Chiligum's fallback option in case of Message Broker being down
+  fallback_broker_config: {
     region: ENV['CHILI_LOGGER_SQS_HANDLER_REGION'],
     access_key_id: ENV['CHILI_LOGGER_SQS_HANDLER_KEY_ID'],
     secret_access_key: ENV['CHILI_LOGGER_SQS_HANDLER_SECRET_KEY'],
@@ -52,31 +295,803 @@ ChiliLogger.instance.config({
   }
 })
 ```
+The attributes `log_env` and `log_layer` set the fields ['env'](###environment) and ['layer'](###layer) in all logs that will be published by ChiliLogger.
+
+When configuring ChiliLogger, you MUST set `msg_broker_name` and `msg_broker_config`. All logs are published to the configured message broker and, without it, ChiliLogger can't work. For the time being, only `:rabbitmq` is supported.
+
+You ALSO MUST set `fallback_broker` and `fallback_broker_config`. This is the fallback option if the Message Broker is not available and, without it, ChiliLogger would break the application every time the Message Broker was down. For the time being, only `:aws_sqs` is supported.
+
+Please note that if ChiliLogger tries to publish a log and both the configured Message Broker and the Error Handler are simultaneously down, the log will be discarded. This behavior makes sure logging problems never cause the app to break.
+
+#### Overwriting RabbitMQ's routing_key
+The [routing_key for all messages sent to rabbit will be created based on the description tag of the log](####description). But, sometimes, specially when testing, you may want to force all messages to be sent with a hardcoded routing_key. In those cases, you can add an optional field to the msg_broker_config: `routing_key_overwriter`.
+```ruby
+ChiliLogger.instance.config({
+  ...
+  msg_broker_name: :rabbitmq,
+  msg_broker_config: {
+    user: ENV['RABBIT_USER'],
+    password: ENV['RABBIT_PASSWORD'],
+    ip: ENV['RABBIT_IP'],
+    port: ENV['RABBIT_PORT'],
+    exchange_name: ENV['RABBIT_EXCHANGE'],
+    routing_key_overwriter: 'a.hardcoded.routing.key'
+  },
+  ...
+})
+```
+
+## Basic Usage
+
+#### publish_instant_log params
+The easiest way to use ChiliLogger is with the `publish_instant_log` method. It requires a hash with the following optional attributes: 
+```ruby
+{
+  desc: { # Hash
+    type: 'transaction', # String,
+    service: 'videos', # String
+    action: 'create', # String
+  },
+  user: { 
+    cognito_id: 100, # String || Fixnum || Bignum -> ChiliLogger converts cognito_id fields with these types to Strings
+    email: 'example@chiligumvideos.com', # String
+    company_cognito_id: 88, # String || Fixnum || Bignum -> ChiliLogger converts company_cognito_id fields with these types to Strings
+    company_name: 'Chiligum', # String
+    ghost_user_cognito_id: 420, # String || Fixnum || Bignum -> ChiliLogger converts ghost_user_cognito_id with these types to Strings
+  },
+  main_content: { # Hash
+    modified_records: {  # Hash
+      "#{tablename}": [ # Array of Hashes
+        { id: 42, title: 'Example video 1' },
+        { id: 42, title: 'Example video 2' },
+      ],
+      "#{another_tablename}": [ # Array of Hashes
+        { id: 42, title: 'Example banner 1' },
+        { id: 42, title: 'Example banner 2' },
+      ],
+    },
+    errors: [ # Array of Strings or Exception descendents -> ChiliLogger converts Exception descendents to Strings
+      'first error',
+      StandardError.new('second error')
+    ]
+  },
+}
+```
+`desc` is used for setting the log's [type](###type), [service](###service), and [action](###action). env and layer were already set when ChiliLogger was [initialized and configured](##installation). Only `type`, `service`, and `action` are accepted.
+
+`user` will set the user data. Only `cognito_id`, `email`, `company_cognito_id`, `company_name`, and `ghost_user_cognito_id` are accepted.
+
+`main_content` will set the main information the log is concerned about. It only accepts `modified_records` or `errors`.
+
+These fields must be set with the appropriate primitive types, as specified above. Not doing so [may create invalid logs](##read-before-contributing). Because of that, ChiliLogger tries its best to enforce that all fields in a log will have consistent primitive types.
+
+
+#### publish_instant_log usage example
+```ruby
+desc = { type: 'transaction', service: 'videos', action: 'create' }
+user = { 
+    cognito_id: 88, 
+    email: 'exemple@test.com',
+    company_cognito_id: 75,
+    company_name: "Chiligum Creatives",
+    ghost_user_cognito_id: 55
+  },
+main_content = { 
+  modified_records: {
+    # notice we have a key 'videos' (the SQS tablename) pointing to an array of hashes
+    videos: [{ id: 42, title: 'Lateralus' }]
+  }
+}
+
+ChiliLogger.instance.publish_instant_log(desc: desc, user: user, main_content: main_content)
+# publishes a json like this:
+{
+  "env": "development",
+  "layer": "creatives",
+  "type": "transaction",
+  "service": "videos",
+  "action": "create",
+  "desc": "development.creatives.transaction.videos.create",
+  "user": { 
+    "cognito_id": "88", 
+    "email": 'exemple@test.com',
+    "company_cognito_id": "75",
+    "company_name": "Chiligum Creatives",
+    "ghost_user_cognito_id": "55"
+  },
+  "transaction": {
+    "modified_records": {
+      "videos": [{ "id": 42, "title": 'Lateralus' }]
+    },
+    "backtrace": [
+      "app/views/dashboard/controllers/videos_controller.rb:17 in block 'create'"
+    ]
+  },
+  "ops_metadata": {
+    "server_url": "https://app.chiligumvideos.com"
+  },
+  "timestamp": "2020-06-30T18:08:59-03:00",
+}
+```
+
+#### publish_instant_log default argument values
+Passing `desc`, `agent`, and `main_content` is optional, since all of them have default values. This is so ChiliLogger is resiliant and doesn't break if any of these arguments is forgotten. But notice that their default values are not very descriptive and it results in low-quality, almost useless logs:
+
+```ruby
+ChiliLogger.instance.publish_instant_log
+# publishes a json like this:
+{
+  "action": "not_specified",
+  "layer": "creatives",
+  "env": "development",
+  "type": "not_specified",
+  "service": "not_specified",
+  "desc": "development.creatives.not_specified.not_specified.not_specified",
+  "user": {
+    "cognito_id": 'not_specified',
+    "email": 'not_specified',
+    "company_cognito_id": 'not_specified',
+    "company_name": 'not_specified',
+    "ghost_user_cognito_id": 'not_specified'
+  }, 
+  "not_specified": {},
+    "backtrace": [
+      "app/views/dashboard/controllers/videos_controller.rb:17 in block 'create'"
+    ]
+  },
+  "ops_metadata": {
+    "server_url": "https://app.chiligumvideos.com"
+  },
+  "timestamp": "2020-06-30T18:08:59-03:00",
+}
+```
+#### ChiliLogger's Singleton pattern
+Notice that ChiliLogger uses the Singleton pattern. So, to call its methods, you must first access the instance method. Calling ChiliLogger.new will return an error:
+```ruby
+ChiliLogger.publish_instant_log(desc, agent, log)
+# undefined method `publish_instant_log' for ChiliLogger:Class
+
+ChiliLogger.new.publish_instant_log(desc, agent, log)
+# NoMethodError: private method `new' called for ChiliLogger:Class
+
+ChiliLogger.instance.publish_instant_log(desc, agent, log)
+# works fine
+```
+
+
+## Advanced Usage
+It will often happen that the information needed for a log is distributed in many parts of the application and can't be accessed in a single moment nor in a single place of the code base. For instance, you may want to set the log's agent with information about the current_user that's only available in the Controllers Layer. And you might want to add data to the log every time a DB record is modified, which is easier to do in the Models Layer. For these use cases, ChiliLogger's `publish_instant_log` will not be suitable and you should use more advanced features.
+
+ChiliLogger takes advantage of Ruby's Thread class and allows you to start a log and keep adding information to it during the current thread's lifespan. This is particularly useful when logging requests to a controller, since these requests will run from beginning to end in a single thread.
+
+Once a log is started, it can be accessed and modified by using ChiliLogger's `start_new_log` method and `current_log` accessor.
+
+#### Advanced Code Example
+```ruby
+# controllers/videos_controller.rb
+class VideosController
+  def create
+    desc = { type: 'transaction', service: 'videos', action: 'create' }
+    agent = { user: current_user.as_json, company: current_user.as_json }
+    current_log = ChiliLogger.instance.start_new_log(desc, agent) # Step One
+
+    Video.create(title: 'Lateralus') # Step Two happens in the Video model
+
+    current_log.publish # Step Three
+  end
+end
+
+# models/video.rb
+class Video < ApplicationRecord
+  after_create :add_modified_record_to_log
+
+  def add_modified_record_to_log
+    current_log = ChiliLogger.instance.current_log
+    modified_record = self.as_json
+
+    current_log.add_modified_record(self.class.table_name, modified_record) # Step Two
+  end
+end
+
+# resulting log (simplified)
+{
+  "env": "development",
+  "layer": "creatives",
+  "type": "transaction",
+  "service": "videos",
+  "action": "create",
+  "desc": "development.creatives.transaction.videos.create",
+  "agent": { 
+    "user": { 
+      "id": 88, 
+      "email": 'exemple@test.com'
+    }, 
+    "company": {
+      "id": 75, 
+      "name": 'Chiligum' 
+    }
+  },
+  "transaction": {
+    "modified_records": {
+      "videos": [{ "id": 42, "title": 'Lateralus' }]
+    },
+    "backtrace": [
+      "app/views/dashboard/controllers/videos_controller.rb:17 in block 'create'"
+    ]
+  },
+  "ops_metadata": {
+    "server_url": "https://app.chiligumvideos.com"
+  },
+  "timestamp": "2020-06-30T18:08:59-03:00",
+}
+```
+
+Notice that the log is started in VideosController#create with some initial info about the agent user and the log description; following, the same log has its main_content customized in Video.add_modified_record_to_log, by accessing ChiliLogger's `current_log` and calling its `add_modified_record` method. And, afterwards, the same log is finished and published with `current_log.publish`, again in VideosController#create.
+
+Check the [Snippets For Quick Logging](##snippets-for-quick-logging) section to see how this functionality can be used to quickly set an all-embracing logging system for your application.
+
+#### Error Logging
+The controller code above could be improved by adding some logic to log unexpected errors:
+```ruby
+# controllers/videos_controller.rb
+class VideosController
+  def create
+    desc = { type: 'transaction', service: 'videos', action: 'create' }
+    agent = { user: current_user.as_json, company: current_user.as_json } # .as_json converts ActiveReacords into Hash
+    current_log = ChiliLogger.instance.start_new_log(desc, agent)
+
+    Video.create(title: 'Lateralus')
+
+    current_log.publish
+
+  rescue StandardError => error
+    #changes log type and publishes it
+    current_log.add_to_main_content({ error: error.as_json })
+    current_log.update_type('uncaught_error')
+    current_log.publish
+  end
+end
+```
+A [full list of methods](###customizing-a-started-log) for customizing a `current_log` is available
+
+### Customizing a Started Log
+Once a log is started, its main attributes can be customized by accessing the `current_log` and calling one of its many customizing methods.
+#### Accessing the current_log
+```ruby
+current_log = ChiliLogger.instance.current_log
+current_log.user # returns currently set user
+current_log.update_user(cognito_id: '42', company_name: 'Chiligum') # updates user data
+```
+#### user
+returns log's currently set user
+
+```ruby
+current_log.user
+# { cognito_id: 'not_specified', email: 'not_specified', company_cognito_id: 'not_specified',
+#   company_name: 'not_specified', ghost_user_cognito_id: 'not_specified' }
+```
+
+---
+
+#### update_user
+updates the currently set user
+
+```ruby
+current_log.user
+# { cognito_id: 'not_specified', email: 'not_specified', company_cognito_id: 'not_specified',
+#   company_name: 'not_specified', ghost_user_cognito_id: 'not_specified' }
+
+current_log.update_user({ email: 'new_email' } })
+current_log.user
+# { cognito_id: 'not_specified', email: 'new_email', company_cognito_id: 'not_specified',
+#   company_name: 'not_specified', ghost_user_cognito_id: 'not_specified' }
+```
+
+---
+
+#### desc
+returns currently set log's description. Notice that, for the time being, `env` and `layer` can't be overwritten, these description attributes can only be set during [ChiliLogger's configuration](##installation)
+
+```ruby
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'not_specified' }
+```
+
+---
+
+#### update_type
+updates the type attribute currently set in the log's description 
+
+```ruby
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'not_specified' }
+
+current_log.update_type('transaction')
+current_log.desc
+# { type: 'transaction', service: 'not_specified', action: 'not_specified' }
+```
+
+---
+
+#### update_service
+updates the service attribute currently set in the log's description 
+
+```ruby
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'not_specified' }
+
+current_log.update_service('videos')
+current_log.desc
+# { type: 'not_specified', service: 'videos', action: 'not_specified' }
+```
+
+---
+
+#### update_action
+updates the action attribute currently set in the log's description 
+
+```ruby
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'not_specified' }
+
+current_log.update_action('delete')
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'delete' }
+```
+
+---
+
+#### update_desc
+updates the currently set log's description
+
+```ruby
+current_log.desc
+# { type: 'not_specified', service: 'not_specified', action: 'not_specified' }
+
+current_log.update_desc({ type: 'uncaught_error', action: 'create' })
+current_log.desc
+# { type: 'uncaught_error', service: 'not_specified', action: 'create' }
+```
+
+---
+
+#### main_content
+returns the currently set main_content
+
+```ruby
+current_log.main_content
+# { modified_records: {}, errors: [] }
+
+```
+
+---
+
+#### update_main_content
+updates the currently set main_content
+
+```ruby
+current_log.main_content
+# { modified_records: {}, errors: [] }
+
+new_content = {
+  modified_records: { 
+    'videos' => [{ title: 'Lateralus', id: 42 }] 
+  }
+}
+current_log.update_main_content(new_content)
+current_log.main_content
+# {
+#   modified_records: { 
+#     'videos' => [{ title: 'Lateralus', id: 42 }] 
+#   },
+#   errors: []
+# }
+```
+
+---
+
+#### add_to_main_content
+merges hash with currently set main_content
+
+```ruby
+current_log.main_content
+# { modified_records: {}, errors: ['err1', 'err2'] }
+
+current_log.add_to_main_content(errors: ['err50'])
+current_log.main_content
+# { modified_records: {}, errors: ['err1', 'err2', 'err50'] }
+```
+
+---
+
+#### modified_records
+returns the modified_records stored in the main_content
+
+```ruby
+current_log.modified_records
+# {}
+```
+
+---
+
+#### overwrite_modified_records
+overwrites the modified_records stored in the main_content
+
+```ruby
+current_log.modified_records
+# { tracks: [{ id: 87, title: 'Hips Dont Lie' }] }
+
+current_log.overwrite_modified_records({ tracks: [{ id: 88, title: 'Lateralus' }] })
+current_log.modified_records
+# { tracks: [{ id: 88, title: 'Lateralus' }] }
+```
+
+---
+
+#### add_modified_record
+merges hash with currently set modified_records. Notice it receives two arguments: the `tablename` and the `record` itself;
+
+```ruby
+current_log.modified_records
+# { tracks: [{ id: 88, title: 'Lateralus' }] }
+
+current_log.add_modified_records('tracks', { id: 89, title: "Hips Don't lie" })
+current_log.modified_records
+# { 
+#   tracks: [{ id: 88, title: 'Lateralus' }, { id: 89, title: "Hips Don't lie" }],
+# }
+
+current_log.add_modified_records('videos', { id: 42, title: 'Life Of Brian' })
+current_log.modified_records
+# { 
+#   tracks: [{ id: 88, title: 'Lateralus' }, { id: 89, title: "Hips Don't lie" }],
+#   videos: [{id: 42, title: 'Life Of Brian' }]
+# }
+```
+
+---
+
+#### errors
+returns the errors stored in the main_content
+
+```ruby
+current_log.errors
+# []
+```
+
+---
+
+#### overwrite_errors
+overwrites the errors stored in the main_content
+
+```ruby
+current_log.errors
+# ['err1', 'err2', 'err3']
+
+current_log.overwrite_errors(['err500'])
+current_log.errors
+# ['err500']
+```
+
+---
+
+#### add_error
+merges hash with currently set errors
+
+```ruby
+current_log.errors
+# ['err1', 'err2', 'err3']
+
+current_log.add_error('err400')
+current_log.errors
+# ['err1', 'err2', 'err3', 'err400']}
+```
+
+#### clear_log_info
+sets agent, desc, and main_content to their default values.
+
+
+## Snippets for Quicker Logging
+Following is a series of snippets for quickly setting up some basic logging functionality. 
+**Please notice that the snippets in this section use the [paper_trail gem](https://github.com/paper-trail-gem/paper_trail/blob/v9.2.0/README.md#1c-basic-usage) for improving logs. Its use is optional, but recommended.**
+
+### Papertrail Optional Use
+
+> ChiliLogger works just fine without paper_trail. If you don't want to use paper_trail or if your application doesn't use ActiveRecords, you can skip the following code.
+>
+> Papertrail allows us to keep a history of changes made to ActiveRecords entities, which is great for logging. To install and setup `paper_trail`, add the following code:
+
+    // optional code if you want to use Papertrail to enrich logs
+    $ bundle add paper_trail
+    $ bundle install
+    $ bundle exec rails generate paper_trail:install
+    $ bundle exec rake db:migrate
+and then:
+```ruby
+# optional code if you want to use Papertrail to enrich logs
+
+# models/application_record.rb
+class ApplicationRecord < ActiveRecord::Base
+  self.abstract_class = true
+
+  has_paper_trail # add this line!
+end
+```
+If your controllers have a current_user, it usually won't be accessible in the models. When implementing logs, though, it is a behaviour you might be interested in, so you can log changes to the DB knowing who was the user responsible for that change. PaperTrail has a feature called `whodunnit`, which is [used precisely for this purpose](https://github.com/paper-trail-gem/paper_trail/blob/v10.3.1/README.md#setting-whodunnit-with-a-controller-callback).
+```ruby
+# controllers/application_controller.rb
+class ApplicationController < ActionController::Base
+  # sets papertrail Whodunit based on user defined in user_for_paper_trail
+  before_action :set_paper_trail_whodunnit
+
+  # customizes method implemented by PaperTrail and that sets PaperTrail.request.whodunit
+  # PaperTrail.request.whodunit will be available in all parts of application while a request is being processed  
+  def user_for_paper_trail
+    current_user
+  end
+end
+```
+
+### Logging Transactions in HTTP Requests
+Transactions happen in two main layers of an application: the controllers handling the request and the models persisting data. If your application has an ApplicationController from which all other controllers inherit, and also an ApplicationRecord from which all models inherit, we can quickly set standardized logs for transactions and errors. 
+
+#### Controllers Logging Logic
+Just add the following code to your ApplicationController:
+```ruby
+# controllers/application_controller.rb
+class ApplicationController < ActionController::Base
+  before_action :start_new_log
+  rescue_from StandardError, with: :publish_error_log
+  after_action :publish_log
+
+  def start_new_log
+    table_name = self.class.name.split('::').last.gsub('Controller', '').underscore
+    # action_name is available in Rails apps, Sinatra apps may need some other solution
+    log_action = action_name == 'destroy' ? 'delete' : action_name
+
+    desc ||= log_description('transaction', table_name, log_action)
+    user = log_user
+
+    ChiliLogger.instance.start_new_log(desc: desc, user: user)
+  end
+
+  # publishes transaction log with the main infos about the request
+  def publish_log
+    # only publish log if current log had modified_records added to it, so we don't clutter logs with index requests
+    return if ChiliLogger.instance.current_log.modified_records.empty?
+
+    ChiliLogger.instance.current_log.publish
+  end
+
+  # if unexpected errors happen, will change log type and publish it for debugging/audit
+  def publish_error_log(error)
+    error = [error.inspect, Rails.backtrace_cleaner.clean(error.backtrace)]
+    current_log = ChiliLogger.instance.current_log
+
+    current_log.add_error(error)
+    current_log.update_type('uncaught_error')
+    current_log.publish
+
+    raise error
+  end
+
+  private
+
+  def log_description(type, service, action)
+    { type: type, service: service, action: action }
+  end
+
+  # customize according to your app's schema
+  def log_user
+    return {} unless current_user
+
+    multi_user_record = MultiUser::User.find(current_user&.cognito_id)
+    log_user = { 
+      email: current_user&.email, 
+      cognito_id: multi_user_record&.id,
+      company_name: current_user&.company&.name,
+      company_cognito_id: multi_user_record&.organization&.id
+    }
+    log_user.merge!(ghost_user_cognito_id: admin_ghost_user&.cognito_id) # if app has admins that can log as other users 
+  end
+end
+```
+ 
+Notice that `start_new_log` will set the log's service and action based on the controller name and the method being called. So if VideosController has its create method called, it would generate a log with service="videos" and action="create". Individual controllers and methods can be customized by using the [current_log accessors](###customizing-a-started-log). 
+
+For example, suppose we would like the GalleryFilesController to generate custom logs with service='gallery' and we would like GalleryFilesController#find_files to define action='filter'. We could do the following:
+```ruby
+# app/controllers/gallery_files.rb
+class GalleryFilesController < ApplicationController
+  before_action :overwrite_log_service
+
+  def find_files
+    ChiliLogger.instance.current_log.update_action('filter')
+    # method's usual code...
+  end
+
+  private
+
+  # customizes logs created by ApplicationController's start_new_log method
+    def overwrite_log_service
+      ChiliLogger.instance.current_log.update_service('gallery')
+    end
+end
+```
+
+#### Models Logging Logic
+The code above implements automatic logs for requests made to controllers. We can further improve the logs being created by adding the DB records that were modified during the request:
+```ruby
+class ApplicationRecord < ActiveRecord::Base
+  self.abstract_class = true
+
+  after_create -> { add_modified_record_to_log('create') }, on: :create
+  after_update -> { add_modified_record_to_log('update') }, on: :update
+  before_destroy -> { add_modified_record_to_log('destroy') }, on: :destroy
+
+  has_paper_trail # if you are using paper_trail
+
+  # enriches logs by automatically adding modified_records to them
+  def add_modified_record_to_log(action_verb, modified_record = self)
+    # only adds to log if record was created, changed or destroyed
+    return if !new_record? && changes.empty? && action_verb != 'destroy'
+
+    current_log = ChiliLogger.instance.current_log
+    current_log.update_type('transaction_error') unless modified_record.errors.messages.empty?
+    current_log.add_modified_record(self.class.table_name, modified_record.to_denormalized_hash)
+  end
+
+  # ChiliLogger requires modified_records to be hashes. 
+  # This method converts ActiveRecords instances to hashes and adds some extra useful data
+  def to_denormalized_hash(record_hash = as_json)
+    record_hash[:last_changes] = versions.last.changeset if versions.last #if you are using paper_trail
+    record_hash[:errors] = errors
+
+    record_hash
+  end
+end
+```
+
+The code above will add all modified records to the transaction logs. We implement a `to_denormalized_hash` method, which converts the ActiveRecord isntance to a hash, as ChiliLogger requires. This method can be customized in individual models, to generate logs with even more information (for instance, denormalizing the main ActiveRecords relations):
+```ruby
+# app/models/banner.rb
+class Banner < ApplicationRecord
+  # customizes inherited ApplicationRecord's method, denormalizing the record's main relations
+  def to_denormalized_hash(record_hash = as_json)
+    relations = Banner.includes(:campaign)
+                      .includes(template: %i[category template_collection])
+                      .find(id)
+
+    record_hash[:campaign] = relations.campaign.as_json
+    record_hash[:template] = relations.template.as_json
+    record_hash[:template][:category] = relations.template.category.as_json
+    record_hash[:template][:template_collection] = relations.template.template_collection.as_json
+
+    super(record_hash) # calls ActiveRecords's to_denormalized_hash
+  end
+end
+```
 
-When configuring ChiliLogger, you MUST set msg_broker_name and msg_broker_config. All logs are published to this message broker and, without it, ChiliLogger can't work. For the time being, only :rabbitmq is supported.
+### Logging Rake Tasks
+When logging transactions made in tasks, we have three main concerns: logging uncaught errors in the task, logging transactions performed by the task and log whether the task is up and running, for monitoring.
 
-You ALSO MUST set error_handler and error_handler_config. The error handler is the fallback option if the message broker is not available and, without it, ChiliLogger will break the application every time the message broker is down. For the time being, only :aws_sqs is supported.
+#### Logging Uncaught Task Errors
+For this, we must create a standardized way of handling task errors. The best wayto do it is with a monkey-patch to rake, by creating the following file:
+```ruby
+# config/initializers/task.rb
+require 'rake/task'
+
+module Rake
+  class Task
+    alias :original_execute :execute
 
-Please note that if ChiliLogger tries to publish a log and both the Message Broker and the Error Handler are simultaneously down, the log will be discarded. This behavior makes sure logging problems never cause the app to break.
+    # customizes the execute method of Rake::Task
+    def execute(args=nil)
+      begin
+        # start storing default log infos for rake tasks before they even begin
+        log_desc = { log_type: 'error', service: 'automated_task', action: 'uncaught_error' }
+        log_user = { email: 'automated_task', cognito_id: 'automated_task' }
+        ChiliLogger.instance.start_new_log(desc: log_desc, user: log_user)
 
+        original_execute(args)
 
+      rescue StandardError => error
+        current_log = ChiliLogger.instance.current_log
 
+        current_log.add_error(error.inspect)
+        current_log.update_type('uncaught_error')
+        current_log.publish
 
-## Usage
+        raise error
+      end
+    end
+  end
+end
+```
+
+#### Logging Transactions in Tasks 
+Unfortunately, for the time being, we still haven't found a practical way to log all Task transactions with minimal setup. The way most of our tasks are implemented - as infinite loops - requires us to add logging logic to each and every task, by doing so:
+```ruby
+# lib/tasks/example_task.rake
+namespace :excel do
+  task validation: :environment do
+    loop do
+      # start storing infos for validation log
+      transaction_desc = { log_type: 'transaction', service: 'excel', action: 'validation' }
+      log_user = { email: 'automated_task', cognito_id: 'automated_task' 
+      current_log = ChiliLogger.instance.start_new_log(desc: log_desc, user: log_user)
 
-TODO: Write usage instructions here
+      usual task code...
+      
+      # only publish log if current log had modified_records added to it - so we don't clutter DB with meaningless logs
+      current_log.publish if current_log.modified_records
 
-## Development
+      sleep 5
+    end
+end
+```
+Until we come up with a better solution, this will have to be done to each and every task of interest. Notice that the snippet above assumes you have [edited the models to enrich logs with modified_records](####models-logging-logic).
+
+#### Logging Heartbeats in Tasks
+Besides monitoring transactions and unexpected errors, it is also important to monitor whether all main parts of an application are up and running. For servers, we do that by pinging specific endpoints to see if the server is up and responding. Tasks pose a different problem, since they have no endpoint we can ping. Besides, a task maybe up and with a 'running' status, but being stuck all the same and not processing new data. For that reason, we use ChiliLogger to monitor tasks' healht. 
+
+Unfortunately, due to the way most of our tasks are implemented - as infinite loops - we must add logging logic to each and every task, by doing so:
+```ruby
+# lib/tasks/example_task.rake
+namespace :excel do
+  task validation: :environment do
+    loop do
+      heartbeat_desc = { log_type: 'monitoring', service: 'excel', action: 'validation' }
+      log_user = { email: 'automated_task', cognito_id: 'automated_task' 
+      ChiliLogger.instance.publish_instant_log(desc: heartbeat_desc, user: log_user)
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+      usual task code...
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+      sleep 5
+    end
+end
 
-## Contributing
+``` 
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/chili_logger.
+## Coverage
+ChiliLogger keeps a coverage report, showing what kinds of logs are being created. This can be usefull to see whether all important points of an application are being satisfactorily monitored and also to have an overview of how these logs description tags are looking like. This coverage report can be found in `app_root/log/chili-logger-coverage.yml`. It is an YAML file with 4 dimensions:
+  - first dimension: type;
+  - second dimension: service;
+  - third dimension: action;
+  - fourth dimension: an array with the backtrace of the last created log to a given type, service and action combination;
 
+```yaml
+transaction: #log's type
+  videos: # log's service
+    create: # log's action
+      - "backtrace_path_1" # backtrace for transaction.videos.create
+      - "backtrace_path_2"
+      - "backtrace_path_3"
+    update: # log's action
+      - "backtrace_path_1" # backtrace for transaction.videos.update
+      - "backtrace_path_2"
+      - "backtrace_path_3"
+  banners:
+    create: # log's action
+      - "backtrace_path_1" # backtrace for transaction.banners.create
+      - "backtrace_path_2"
+      - "backtrace_path_3"
+    accept: # log's action
+      - "backtrace_path_1" # backtrace for transaction.banners.accept
+      - "backtrace_path_2"
+      - "backtrace_path_3"
 
-## License
+uncaught_error: #log's type
+  gallery: # log's service
+    index: # log's action
+      - "backtrace_path_1" # backtrace for uncaught_error.gallery_index
+      - "backtrace_path_2"
+      - "backtrace_path_3"
 
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+monitoring: #log's type
+  campaigns: # log's service
+    validate_sheet: # log's action
+      - "backtrace_path_1" # backtrace for monitoring.campaigns.validate_sheet
+      - "backtrace_path_2"
+      - "backtrace_path_3"
+```