sapience 2.0.3 → 2.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a496d597a7e40d5578684eb7c6cb8dcd95f52e7e
-  data.tar.gz: 0f040171526449771d60df6b210bcefb0872a1db
+  metadata.gz: 5ff125a3d5585789c2c8b1ffbd82b54c1b8b73f1
+  data.tar.gz: ed7db99c18a59d7c9f5373bb1ad380fb3f9f00e3
 SHA512:
-  metadata.gz: b9a04aedb193c4a03b77e137c26c866b14961448c376a602301ce96cf5f30e70ef0d551f75aec3eef82c43a262b05529c79d4f2d3e42d04059d79467be334a1a
-  data.tar.gz: 0f3e82c77af85a5a2acd9554811ddd833c6cdbe38939ddc643637a28305eb7491057e0c8448401eab68fbb80f8cc689b08375aa5c2be883d73451a67090bcfed
+  metadata.gz: 8d0c2d599305507f04bc0174dacbbf0dc1e1b19429d2240b2162c26278dc3055c9b6e5e462dc2325c0db01d0f9b728a43b11a1d0ea4863a8054819a67412b5a8
+  data.tar.gz: 3e4053c56cb085397b24df71b3a8ee0de28c0713e2565ba44416f153cb056350c22807878ad69a78301774d1098e5ba4453ef3834f3193c778ed423cfb39bbf3

data/.travis.yml

@@ -22,7 +22,9 @@ before_script:
 script:
   - bundle exec rake reevoocop
   - docker-compose run rspec
-  - docker-compose run rails
+  - docker-compose run rails32
+  - docker-compose run rails42
+  - docker-compose run rails50
   - docker-compose run grape
 
 after_success:

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## v2.0.4
+
+- Fix Sapience.logger. From now it logs into all configured Stream appenders.
+
 ## v2.0.3
 
 - Ability to configure ActiveRecord log level independently

data/README.md

@@ -12,7 +12,7 @@ This project aims to make it easier to centralise the configuration of these thr
 
 We have taken a great deal of inspiration from the amazing [Semantic Logger](https://github.com/rocketjob/semantic_logger) and implemented something similar to [Rubocop](https://github.com/bbatsov/rubocop) for handling and overriding how to find configuration. If you want some inspiration for how we do something similar for our projects for Rubocop check: [Reevoocop](https://github.com/reevoo/reevoocop).
 
-## Setup
+## Installation
 
 First of all we need to require the right file for the project. There are currently two frameworks supported (rails and grape).
 
@@ -38,7 +38,7 @@ module Aslan
     class Base < Grape::API
       use Sapience::Extensions::Grape::Middleware::Logging, logger: Sapience[self]
 
-      # To log all requests even when no route was found add the following:
+      # To log all requests even when no route was found use the following:
       route :any, "*path" do
         error!({ error: "No route found" }, 404)
       end
@@ -78,234 +78,109 @@ rescue_from :all do |e|
 end
 ```
 
+**Note**: if you already have got your grape applications sprinkled with calls to API.logger, and you do 
+not want to have to replace all those calls to Sapience.logger manually, then just re-assign your logger
+after including the Sapience middleware, like below:
 
+```ruby
+use Sapience::Extensions::Grape::Middleware::Logging, logger: Sapience[self]
+API.logger = Sapience.logger
+```
 
-### Configuration
 
-The sapience configuration can be controlled by a `config/sapience.yml` file or if you like us have many projects that use the same configuration you can create your own gem with a shared config. Have a look at [reevoo/reevoo_sapience-rb](https://github.com/reevoo/reevoo_sapience-rb)
+**Note**: If you're using the rackup command to run your server in development, pass the -q flag to silence the default 
+rack logger so you don't get double logging.
 
-The `app_name` is required to be configured. Sapience will fail on startup if app_name isn't configured properly.
 
-```ruby
-Sapience.configure do |config|
-  config.default_level   = :info
-  config.log_level_active_record = :debug
-  config.backtrace_level = :error
-  config.appenders       = [
-    { stream: { io: STDOUT, formatter: :color } },
-    { sentry: { dsn: "https://username:password@sentry.io/00000" } },
-  ]
-  config.log_executor    = :single_thread_executor
-end
-```
+## Configuration
+
+The sapience configuration can be controlled by either a "sapience.yml" file, or a block of ruby code. Note that if you provide both, the block of ruby code will take precedence.
+
+#### Configuration by sapience.yml file
 
-Sapience provides a default configuration that will be used unless another file or configuration is specified. You can provide a custom
+Add a `config/sapience.yml` file to you appplication. Or if you, like us, have many projects that use the same configuration you can create your own gem with a shared .yml config. Have a look at [reevoo/reevoo_sapience-rb](https://github.com/reevoo/reevoo_sapience-rb) for an example . See below an example of how to configure "sapience.yml":
 
 ```yaml
----
 default:
+  app_name: My Application
+  log_level: debug
+  log_level_active_record: info
+  appenders:
+    - stream:
+        io: STDOUT
+        formatter: json
   filter_parameters:
     - password
     - password_confirmation
-  log_executor: single_thread_executor
-  log_level: info
+
+development:
+  log_level: debug
+  metrics:
+    datadog:
+      url: <%= ENV.fetch("STATSD_URL", "udp://localhost:8125") %>
   appenders:
     - stream:
         io: STDOUT
         formatter: color
-
-test:
-  log_executor: immediate_executor
-  log_level: warn
-  appenders:
     - stream:
-        file_name: log/test.log
+        file_name: log/development.log
         formatter: color
-
-development:
-  log_executor: single_thread_executor
-  log_level_active_record: debug
-  log_level: debug
+        
+staging:
+  log_level: info
+  error_handler:
+    sentry:
+      dsn: <%= ENV['SENTRY_DSN'] %>
+  metrics:
+    datadog:
+      url: <%= ENV.fetch("STATSD_URL", "udp://localhost:8125") %>
   appenders:
     - stream:
-        file_name: log/development.log
-        formatter: color
-
+        io: STDOUT
+        formatter: json
+        
 production:
-  log_executor: single_thread_executor
-  log_level: warn
+  log_level: info
+  error_handler:
+    sentry:
+      dsn: <%= ENV['SENTRY_DSN'] %>
+  metrics:
+    datadog:
+      url: <%= ENV.fetch("STATSD_URL", "udp://localhost:8125") %>
   appenders:
     - stream:
-        file_name: log/production.log
+        io: STDOUT
         formatter: json
 ```
 
-
-#### Configuration Inheritance
-
-We will use our default (or overriden - see [reevoo_sapience-rb](https://github.com/reevoo/reevoo_sapience-rb) for more info) configuration as a base. Any configuration specified inside a `config/sapience.yml` file will then me merged into the default or overridden config.
-
-The merge will take place not at the top level but at the environment level. This means that everything inside the environment keys will be replaced with a more specific application config.
-
-Then if a configure block is used that will take presedence.
-
-#### App name
-
-Sapience requires an application name to be set for your logs and such. We decided not to guess what name you want to give your application so there will be no magic involved here. There are 3 different ways of configuring the app_name for Sapience.
-
-##### Environment variables
-
-This is the preferable way. If you have many environments look into using something like dotenv locally and use the power of devops and automation for your production environments.
-
-```bash
-APP_NAME="My Application" bundle exec rails server -p 9000
-```
-
-##### Configuration file
-
-If you are in need of overriding the sapience default configuration an app_name can be used for any environment but we recommend you specify the app_name for the default section. That way you don't have to specify app_name for each environment and avoid some duplicated keys. Of course if you need to specify different app names for various environments by all means do.
-
-```yaml
----
-default:
-  app_name: My Application
-```
-
-##### Configuration block
-
-This will be the top priority and is the first check. The reasoning is that if someone has taken the time to use configure with a block that should override anything set in file configuration or environment.
+#### Configuration by a block of Ruby code
 
 ```ruby
-Sapience.configure do |config|
+Sapience.configure(force: true) do |config|
   config.app_name = "My Application"
+  config.default_level   = :info
+  config.log_level_active_record = :info
+  config.backtrace_level = :error
+  config.filter_parameters = %w(password password_confirmation)
+  config.appenders       = [
+      { stream: { io: STDOUT, formatter: :color } },
+      { stream: { file_name: "log/json_output.log", formatter: :json } }
+  ]
+  config.error_handler = { sentry: { dsn: ENV["SENTRY_DSN"] } }
+  config.metrics = { datadog: { url: ENV["STATSD_URL"] } }
+  config.log_executor    = :single_thread_executor
 end
 ```
 
-#### Filtering out sensitive data
-
-**NOTE: This is intended for (and will currently only work with) Rack-like applications, which include a `params` key in their `payload` hash**
-
-You may not want to log certain parameters which have sensitive information to be in the logs, e.g. `password`.  This can be set using the `filter_parameters` option when using `configure`:
-
-```ruby
-Sapience.configure do |config|
-  # Filter the value of "foo" from rack's parameter hash
-  config.filter_parameters << 'foo'
-end
-```
-
-Note that by default this is set to `['password', 'password_confirmation']`, so be careful when explicitly setting, as you may lose this filtering:
-
-```ruby
-Sapience.configure do |config|
-  # NOTE: password and password_confirmation will no longer be filtered
-  config.filter_parameters = ['foo']
-end
-```
-
-Similarly, *be particularly careful* when setting as `yaml` because this will no longer filter `password` and `password_confirmation`:
-
-```yaml
-some_environment:
-  # NOTE: password and password_confirmation will no longer be filtered if they're not included in this list
-  filter_parameters:
-    - foo
-```
-
-Any filtered parameter will still show in the `params` field, but it's value will be `[FILTERED]`.
-
-## Appenders
-
-One of the things that did not suit us so well with the Semantic Logger approach was that they made a distinction between metrics and appenders. In our view anything that could potentially log something somewhere should be treated as an appender.
-
-There are a number of appenders that each listen to different events and act on its data. It is possible to specify the `level` and `backtrace_level` for each appender by providing (example) `level: :error` to the add_appender method.
-
-
-### Stream
-
-Stream appenders are basically a log stream. You can add as many stream appenders as you like logging to different locations.
-
-```ruby
-Sapience.add_appender(:stream, file: "log/sapience.log", formatter: :json)
-Sapience.add_appender(:stream, io: STDOUT, formatter: :color, level: :trace)
-```
-
-### Sentry
-
-The sentry appender handles sending errors to [sentry](https://sentry.io). It's backtrace and log level can be configured by for instance `level: :info` and `backtrace_level: :debug`. The `level` configuration tells sentry to log starting at that level while the `backtrace_level` tells sentry to only collect backtrace starting at that level.
-
-```ruby
-Sapience.add_appender(
-  :sentry,
-  dsn: "https://username:password@app.getsentry.com/00000",
-  level: :error,
-  backtrace_level: :error
-)
-```
-
-#### Test exceptions
-
-If you want to quickly verify that your appenders are handling exceptions properly. You can use the following method to
-generate and log an exception at any given level.
-
-```ruby
-Sapience.test_exception(:error)
-```
-
-### Datadog
-
-Datadog is a slightly modified version of statsd. On top of the standard statsd API it has support for events.
-
-```ruby
-Sapience.add_appender(:datadog, url: "udp://localhost:8125")
-```
-
-The appender will then be listening to anything that is logged with a `metric: "company/project/metric-name"` key. Details about the API can be found in [dogstatsd-ruby](https://github.com/DataDog/dogstatsd-ruby).
-
-The appender can also be used directly through: `Sapience.metrics`
-
-```ruby
-metrics = Sapience.metrics
-metrics.timing("company/project/metric-name", 100)
-metrics.increment("company/project/metric-name", 10)
-metrics.decrement("company/project/metric-name", 5)
-metrics.histogram("company/project/metric-name", 2_500)
-metrics.gauge("company/project/metric-name", 1_000, {})
-metrics.event("company/project/metric-name", "description about event", {})
-metrics.batch do
-  metrics.event("company/project/metric-name", "description about event", {})
-  metrics.increment("company/project/another-metric-name", 2)
-end
-```
-
+For further details about "app_name", "filter_parameters", "appenders", "metrics" and "error_handler" used in both the .yml and the code configurations above, see the links below:
 
-### Wrapper
+- [app_name](docs/app_name.md)
+- [filter_parameters](docs/filter_parameters.md)
+- [appenders](docs/appenders.md)
+- [metrics](docs/metrics.md)
+- [error_handler](docs/error_handler.md)
+- [logger](docs/logger.md)
 
-The wrapper is useful when you already have a logger you want to use but want to use Sapience. The wrapper appender will when called use the logger provided to store the log data.
-
-```ruby
-Sapience.add_appender(:wrapper, logger: Logger.new(STDOUT))
-```
-
-## Formatters
-
-Formatters can be specified by using the key `formatter: :camelized_formatter_name`. **Note**: Only the File appender supports custom formatters.
-
-### Color
-
-`formatter: :color` - gives colorized output. Useful for `test` and `development` environments.
-
-### Default
-
-`formatter: :default` - logs a string. Inspired by how access logs for Nginx are logged.
-
-### JSON
-
-`formatter: :json` - logs are saved as a single line json. Useful for production like environments.
-
-### RAW
-
-`formatter: :raw` - logs are saved as a single line ruby hash. Useful for production like environments and is used internally for the Sentry appender.
 
 ## Running the tests
 
@@ -313,6 +188,8 @@ You need to create the test postgres db, by running the command below:
 
 `createdb rails_app_test`
 
+Then you can run them with the followign command:
+
 `bin/tests`
 
 ## Environment variables
@@ -320,9 +197,6 @@ You need to create the test postgres db, by running the command below:
 - `APP_NAME` - If you want to provide an application name for sapience it can be done here.
 - `SAPIENCE_ENV` - For applications that don't use rack or rails
 
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/reevoo/sapience. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
 
 
 ## License

data/docker-compose.yml

@@ -52,24 +52,56 @@ services:
 
 
 
-  rails:
+  rails32:
     extends:
       service: base
-    working_dir: /usr/src/app/test_apps/rails
+    working_dir: /usr/src/app/test_apps/rails_3_2
     entrypoint: /usr/src/app/dev-entrypoint.sh
     command: bundle exec rspec
     depends_on:
       - rabbitmq
       - postgres
     environment:
-      APP_NAME: rails_app
+      APP_NAME: rails_3_2
       POSTGRES_HOST: postgres
       POSTGRES_USER: sapience
       POSTGRES_PASSWORD: tests
       AMQP: amqp://sapience:tests@rabbitmq:5672
       PATH: /usr/src/app/bin:/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
+  rails42:
+    extends:
+      service: base
+    working_dir: /usr/src/app/test_apps/rails_4_2
+    entrypoint: /usr/src/app/dev-entrypoint.sh
+    command: bundle exec rspec
+    depends_on:
+      - rabbitmq
+      - postgres
+    environment:
+      APP_NAME: rails_4_2
+      POSTGRES_HOST: postgres
+      POSTGRES_USER: sapience
+      POSTGRES_PASSWORD: tests
+      AMQP: amqp://sapience:tests@rabbitmq:5672
+      PATH: /usr/src/app/bin:/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
+  rails50:
+    extends:
+      service: base
+    working_dir: /usr/src/app/test_apps/rails_5_0
+    entrypoint: /usr/src/app/dev-entrypoint.sh
+    command: bundle exec rspec
+    depends_on:
+      - rabbitmq
+      - postgres
+    environment:
+      APP_NAME: rails_5_0
+      POSTGRES_HOST: postgres
+      POSTGRES_USER: sapience
+      POSTGRES_PASSWORD: tests
+      AMQP: amqp://sapience:tests@rabbitmq:5672
+      PATH: /usr/src/app/bin:/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
   grape:
     extends:

data/docs/app_name.md

@@ -0,0 +1,32 @@
+
+#### App name
+
+Sapience requires an application name to be set for your logs and such. We decided not to guess what name you want to give your application so there will be no magic involved here. There are 3 different ways of configuring the app_name for Sapience.
+
+##### Environment variables
+
+This is the preferable way. If you have many environments look into using something like dotenv locally and use the power of devops and automation for your production environments.
+
+```bash
+APP_NAME="My Application" bundle exec rails server -p 9000
+```
+
+##### Configuration file
+
+If you are in need of overriding the sapience default configuration an app_name can be used for any environment but we recommend you specify the app_name for the default section. That way you don't have to specify app_name for each environment and avoid some duplicated keys. Of course if you need to specify different app names for various environments by all means do.
+
+```yaml
+---
+default:
+  app_name: My Application
+```
+
+##### Configuration block
+
+This will be the top priority and is the first check. The reasoning is that if someone has taken the time to use configure with a block that should override anything set in file configuration or environment.
+
+```ruby
+Sapience.configure do |config|
+  config.app_name = "My Application"
+end
+```

data/docs/appenders/formatters.md

@@ -0,0 +1,20 @@
+## Formatters
+
+Formatters can be specified by using the key `formatter: :camelized_formatter_name`. **Note**: Only the File appender supports custom formatters.
+
+### Color
+
+`formatter: :color` - gives colorized output. Useful for `test` and `development` environments.
+
+### Default
+
+`formatter: :default` - logs a string. Inspired by how access logs for Nginx are logged.
+
+### JSON
+
+`formatter: :json` - logs are saved as a single line json. Useful for production like environments.
+
+### RAW
+
+`formatter: :raw` - logs are saved as a single line ruby hash. Useful for production like environments and is used internally for the Sentry appender.
+

data/docs/appenders.md

@@ -0,0 +1,37 @@
+We have two different types of appenders, see below.
+
+
+## Stream
+
+
+Stream appenders are basically a log stream. You can add as many stream appenders as you like logging to different locations.
+
+```ruby
+Sapience.add_appender(:stream, file: "log/sapience.log", formatter: :json)
+Sapience.add_appender(:stream, io: STDOUT, formatter: :color, level: :trace)
+```
+
+or using the sapience.yml file:
+
+```yml
+appenders:
+ - stream:
+     io: STDOUT
+     formatter: color
+ - stream:
+     file_name: log/development.log
+     formatter: color
+```
+You can specify the formatter for each stream, click in the link below to see the list of formatters available:
+
+- [formatters](appenders/formatters.md)
+
+
+
+### Wrapper
+
+The wrapper is useful when you already have a logger you want to use but want to use Sapience. The wrapper appender will when called use the logger provided to store the log data.
+
+```ruby
+Sapience.add_appender(:wrapper, logger: Logger.new(STDOUT))
+```

data/docs/contributing/README.md

@@ -0,0 +1,3 @@
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/reevoo/sapience. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.

data/docs/error_handler.md

@@ -0,0 +1,42 @@
+## Error Handling
+
+At the moment we only support [sentry](https://sentry.io) for error alerting.
+
+You can configure the sentry DNS through "sapience.yml", using the "error_handler" section shown in the example below.
+(note that you can use an environment variable, as in the example below, or just put the DNS in plain text if you prefer).
+```yml
+production:
+  log_level: info
+
+  error_handler:
+    sentry:
+      dsn: <%= ENV['SENTRY_DSN'] %>
+
+```
+or through ruby code as below:
+
+```ruby
+Sapience.error_handler = { sentry: { dsn: ENV["SENTRY_DSN"] } }
+```
+Then you can send error messages to Sentry using the following two public methods in Sapience:
+
+```ruby
+  capture_exception(exception, payload = {})
+  capture_message(message, payload = {})
+```
+
+As in the example below:
+```ruby
+begin
+  (do somehting)
+rescue MyException => e
+  Sapience.capture_exception(e)
+  raise e
+end
+```
+
+You can also test that you've configured the DNS correctly by using the "test_exception" method, that will send a test message to your configured Sentry project. See below.
+
+```ruby
+Sapience.test_exception(:error)
+```

data/docs/filter_parameters.md

@@ -0,0 +1,32 @@
+## Filtering out sensitive data
+
+**NOTE: This is intended for (and will currently only work with) Rack-like applications, which include a `params` key in their `payload` hash**
+
+You may not want to log certain parameters which have sensitive information to be in the logs, e.g. `password`.  This can be set using the `filter_parameters` option when using `configure`:
+
+```ruby
+Sapience.configure do |config|
+  # Filter the value of "foo" from rack's parameter hash
+  config.filter_parameters << 'foo'
+end
+```
+
+Note that by default this is set to `['password', 'password_confirmation']`, so be careful when explicitly setting, as you may lose this filtering:
+
+```ruby
+Sapience.configure do |config|
+  # NOTE: password and password_confirmation will no longer be filtered
+  config.filter_parameters = ['foo']
+end
+```
+
+Similarly, *be particularly careful* when setting as `yaml` because this will no longer filter `password` and `password_confirmation`:
+
+```yaml
+some_environment:
+  # NOTE: password and password_confirmation will no longer be filtered if they're not included in this list
+  filter_parameters:
+    - foo
+```
+
+Any filtered parameter will still show in the `params` field, but it's value will be `[FILTERED]`.

data/docs/logger.md

@@ -0,0 +1,42 @@
+## Logger
+
+Our logger implementation is a little different than the standard ruby logger API provides. Our parameters are treated slightly differently and we have more methods on the logger implementation.
+
+### logger.fatal
+
+### logger.error
+
+### logger.warn
+
+### logger.info
+
+### logger.debug
+
+### logger.trace
+
+### logger.measure_fatal
+
+### logger.measure_error
+
+### logger.measure_warn
+
+### logger.measure_info
+
+### logger.measure_debug
+
+### logger.measure_trace
+
+### logger.benchmark_fatal
+
+### logger.benchmark_error
+
+### logger.benchmark_warn
+
+### logger.benchmark_info
+
+### logger.benchmark_debug
+
+### logger.benchmark_trace
+
+### logger.measure
+

data/docs/metrics.md

@@ -0,0 +1,51 @@
+## Metrics
+
+For metrics, at the moment, we only support Datadog.
+
+Datadog is a slightly modified version of statsd. On top of the standard statsd API it has support for events.
+
+You can configure datadog through "sapience.yml", using the "metrics" section shown in the example below.
+(note that you can use an environment variable, as in the example below, or just put the URL in plain text if you prefer).
+```yml
+production:
+  log_level: info
+ 
+  metrics:
+    datadog:
+      url: <%= ENV.fetch("STATSD_URL", "udp://localhost:8125") %>
+```
+or through ruby code as below:
+
+```ruby
+Sapience.metrics = { datadog: { url: ENV["STATSD_URL"] } }
+```
+
+Of course, whatever url you use (like for example "udp://localhost:8125"), make sure you have launched the Datadog agent listening to that host and url. See how to install a Datadog agent in the [Datadog Agent Documentation](http://docs.datadoghq.com/guides/basic_agent_usage/).
+
+Then you can send error metrics to Datadog using  the following methods:
+```ruby
+timing(metric, duration = 0, options = {})
+increment(metric, options = {})
+decrement(metric, options = {})
+histogram(metric, amount, options = {})
+gauge(metric, amount, options = {})
+count(metric, amount, options = {})
+time(metric, options = {}, &block)
+batch(&block)
+event(title, text, options = {})
+```
+
+As in the examples below:
+```ruby
+metrics = Sapience.metrics
+metrics.timing("company/project/metric-name", 100)
+metrics.increment("company/project/metric-name", 10)
+metrics.decrement("company/project/metric-name", 5)
+metrics.histogram("company/project/metric-name", 2_500)
+metrics.gauge("company/project/metric-name", 1_000, {})
+metrics.event("company/project/metric-name", "description about event", {})
+metrics.batch do
+  metrics.event("company/project/metric-name", "description about event", {})
+  metrics.increment("company/project/another-metric-name", 2)
+end
+```

data/lib/sapience/logger.rb

@@ -50,16 +50,13 @@ module Sapience
     end
 
     @@appender_thread = nil
+    @@logger = nil
 
     # Internal logger for Sapience
     #   For example when an appender is not working etc..
     #   By default logs to STDERR
     def self.logger
-      @@logger ||= begin
-        l      = Sapience::Appender::Stream.new(io: STDERR, level: :warn)
-        l.name = name
-        l
-      end
+      @@logger ||= Sapience[Sapience]
     end
 
     # Start the appender thread

data/lib/sapience/metrics/datadog.rb

@@ -18,7 +18,7 @@ module Sapience
       # Parameters:
       #   level: :trace
       #   url: [String]
-      #     Valid URL to post to.
+      #     Valid URL to postdogstatsd-ruby to.
       #     Example:
       #       udp://localhost:8125
       #     Example, send all metrics to a particular namespace:

data/lib/sapience/sapience.rb

@@ -217,10 +217,10 @@ module Sapience
   #   logger = Sapience['Example']
   #   logger.info "Hello World"
   #   logger.debug("Login time", user: 'Joe', duration: 100, ip_address: '127.0.0.1')
-  def self.add_appender(appender, options = {}, _deprecated_level = nil, &_block) # rubocop:disable AbcSize
+  def self.add_appender(appender_class_name, options = {}, _deprecated_level = nil, &_block) # rubocop:disable AbcSize
     fail ArgumentError, "options should be a hash" unless options.is_a?(Hash)
     options        = options.dup.deep_symbolize_keyz!
-    appender_class = constantize_symbol(appender)
+    appender_class = constantize_symbol(appender_class_name)
     validate_appender_class!(appender_class)
 
     appender = appender_class.new(options)
@@ -230,7 +230,6 @@ module Sapience
     # Start appender thread if it is not already running
     Sapience::Logger.start_appender_thread
     Sapience::Logger.start_invalid_appenders_task
-    Sapience.logger = appender if appender.is_a?(Sapience::Appender::Stream)
     appender
   end
 

data/lib/sapience/version.rb

@@ -1,3 +1,3 @@
 module Sapience
-  VERSION = "2.0.3"
+  VERSION = "2.0.4"
 end

data/lib/tasks/coverage.rake

@@ -22,7 +22,7 @@ namespace :coverage do
     require "simplecov-html"
     require "simplecov-json"
 
-    coverage_file_pattern = "{rails,sapience,grape}/.resultset.json"
+    coverage_file_pattern = "{rails_3_2,rails_4_2,rails_5_0,sapience,grape}/.resultset.json"
     json_files = Dir[File.join(coverage_dir, coverage_file_pattern)]
 
     merged_hash = {}
@@ -60,9 +60,7 @@ namespace :coverage do
     ENV["CODECLIMATE_REPO_TOKEN"] = "204dc055302da6aed94379e249aa0645636d1d1794920c62db05c5fa968215de"
     resultset_file   = File.join(coverage_dir, ".resultset.json")
     result_hash      = JSON.parse(File.read(resultset_file))
-    simplecov_result = SimpleCov::Result.from_hash(result_hash)
-
-    CodeClimate::TestReporter::Formatter.new.format(simplecov_result)
+    CodeClimate::TestReporter::Formatter.new.format(result_hash)
     unhide_coverage_config
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sapience
 version: !ruby/object:Gem::Version
-  version: 2.0.3
+  version: 2.0.4
 platform: ruby
 authors:
 - Mikael Henriksson
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-02-16 00:00:00.000000000 Z
+date: 2017-02-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: concurrent-ruby
@@ -300,6 +300,14 @@ files:
 - config/default.yml
 - dev-entrypoint.sh
 - docker-compose.yml
+- docs/app_name.md
+- docs/appenders.md
+- docs/appenders/formatters.md
+- docs/contributing/README.md
+- docs/error_handler.md
+- docs/filter_parameters.md
+- docs/logger.md
+- docs/metrics.md
 - lib/sapience.rb
 - lib/sapience/ansi_colors.rb
 - lib/sapience/appender.rb