l2meter 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 40d1c2183d4a15841d0168f89a86129abb62529e
-  data.tar.gz: 082117b2cd889757d66a5dac5917f80b8efc5c66
+  metadata.gz: ff38c2bf5a18c7b5ef4e31ad3c666fbee6b407cb
+  data.tar.gz: 31669b5e89ec8eb3e796cedbdf9d68f82a845bcc
 SHA512:
-  metadata.gz: 527b9f2e413aef171839b4f08b73bb4ce6644de747c5282ae605b9d18130352eefa5c4dd954f6708c57d639c3bfff039eaf39f5496d22282898fab2ff372a487
-  data.tar.gz: 8af3ee95912957dd530818d75169fe823724ecf83348bf7f2a29505912f7172e679ca70975cbf01b02b9d73a84dda9a4961fea93cc03aeb569b8d81f1b77e158
+  metadata.gz: 0cb1ac63e7dc949d269197cfc058eb76bb37f30c481dfe0067857b0c0075e839fa7a01026e57949d73709abe343bf3a22cb8ffab643f151dc86bd69f7e00a8d6
+  data.tar.gz: 9f776b18885290732ddff9c4b03d56fb5cbbb70f04af7bce286d3580f3a66d932941b9565afc93336fe1399bfdcd33fe3a3c704d56681b0dd96f5712cd0ee787

data/README.md

@@ -11,7 +11,7 @@ l2met-friendly format.
 A new logger might be created like so:
 
 ```ruby
-metrics = L2meter.build
+Metrics = L2meter.build
 ```
 
 If you plan to use it globally across different components of your app,consider
@@ -21,8 +21,8 @@ The base `log` method accepts two type of things: bare values and key-value
 pairs in form of hashes.
 
 ```ruby
-metrics.log "Hello world"                 # => hello-world
-metrics.log :db_query, result: :success   # => db-query result=success
+Metrics.log "Hello world"                 # => hello-world
+Metrics.log :db_query, result: :success   # => db-query result=success
 ```
 
 It can also take a block. In this case the message will be emitted twice, once
@@ -30,9 +30,9 @@ at the start of the execution and another at the end. The end result might look
 like so:
 
 ```ruby
-metrics.log :doing_work do            # => doing-work at=start
+Metrics.log :doing_work do            # => doing-work at=start
   do_some_work                        #
-  metrics.log :work_done              # => work-done
+  Metrics.log :work_done              # => work-done
 end                                   # => doing-work at=finish elapsed=1.2345s
 ```
 
@@ -40,7 +40,7 @@ In case the exception is raised inside the block, l2meter will report is like
 so:
 
 ```ruby
-metrics.log :doing_work do  # => doing-work
+Metrics.log :doing_work do  # => doing-work
   raise ArgumentError, \    #
     "something is wrong"    #
 end                         # => doing-work at=exception exception=ArgumentError message="something is wrong" elapsed=1.2345s
@@ -54,7 +54,7 @@ L2meter allows setting context for a block. It might work something like this:
 def do_work_with_retries
   attempt = 1
   begin
-    metrics.context attempt: attempt do
+    Metrics.context attempt: attempt do
       do_some_work            # => doing-work attempt=1
                               # => doing-work attempt=2
                               # => doing-work attempt=3
@@ -67,14 +67,14 @@ end
 ```
 
 L2meter supports dynamic contexts as well. You can pass a proc instead of raw
-value in porder to use it.
+value in order to use it.
 
-The same example as above could be written like ths instead:
+The same example as above could be re-written like this instead:
 
 ```ruby
 def do_work_with_retries
   attempt = 1
-  metrics.context ->{{ attempt: attempt }} do
+  Metrics.context ->{{ attempt: attempt }} do
     begin
       do_some_work
     rescue => error
@@ -90,22 +90,22 @@ end
 Some other l2met-specific methods are supported.
 
 ```ruby
-metrics.count :user_registered             # => count#user-registered=1
-metrics.count :registered_users, 10        # => count#registered-users=10
+Metrics.count :user_registered             # => count#user-registered=1
+Metrics.count :registered_users, 10        # => count#registered-users=10
 
-metrics.measure :connection_count, 20      # => measure#connection-count=20
-metrics.measure :db_query, 235, unit: :ms, # => measure#db-query.ms=235
+Metrics.measure :connection_count, 20      # => measure#connection-count=20
+Metrics.measure :db_query, 235, unit: :ms, # => measure#db-query.ms=235
 
-metrics.sample :connection_count, 20,      # => sample#connection-count=235
-metrics.sample :db_query, 235, unit: :ms,  # => sample#db-query.ms=235
+Metrics.sample :connection_count, 20,      # => sample#connection-count=235
+Metrics.sample :db_query, 235, unit: :ms,  # => sample#db-query.ms=235
 
-metrics.unique :user, "bob@example.com"    # => unique#user=bob@example.com
+Metrics.unique :user, "bob@example.com"    # => unique#user=bob@example.com
 ```
 
 L2meter also allows to append elapsed time to your log messages automatically.
 
 ```ruby
-metrics.with_elapsed do
+Metrics.with_elapsed do
   do_work_step_1
   log :step_1_done # => step-1-done elapsed=1.2345s
   do_work_step_2
@@ -118,7 +118,7 @@ end
 L2meter supports configuration. Here's how you can configure things:
 
 ```ruby
-metrics = L2meter.build do |config|
+Metrics = L2meter.build do |config|
   # configuration happens here
 end
 ```
@@ -134,7 +134,7 @@ config.context = { app_name: "my-app-name" }
 
 # ...
 
-metrics.log foo: :bar # => app-name=my-app-name foo-bar
+Metrics.log foo: :bar # => app-name=my-app-name foo-bar
 ```
 
 Dynamic context is also supported:
@@ -155,7 +155,7 @@ config.sort = true
 
 # ...
 
-metrics.log :c, :b, :a  # => a b c
+Metrics.log :c, :b, :a  # => a b c
 ```
 
 #### Source
@@ -167,7 +167,7 @@ config.source = "production"
 
 # ...
 
-metrics.log foo: :bar # => source=production foo=bar
+Metrics.log foo: :bar # => source=production foo=bar
 ```
 
 #### Prefix
@@ -179,7 +179,7 @@ config.prefix = "my-app"
 
 # ...
 
-metrics.count :users, 100500 # => count#my-app.users=100500
+Metrics.count :users, 100500 # => count#my-app.users=100500
 ```
 
 ## Silence
@@ -188,13 +188,13 @@ There's a way to temporary silence the log emitter. This might be userful for
 tests for example.
 
 ```ruby
-metrics.silence do
+Metrics.silence do
   # logger is completely silenced
-  metrics.log "hello world" # nothing is emitted here
+  Metrics.log "hello world" # nothing is emitted here
 end
 
 # works normally again
-metrics.log :foo            # => foo
+Metrics.log :foo            # => foo
 ```
 
 The typical setup for RSpec might look like this:

data/lib/l2meter/emitter.rb

@@ -73,7 +73,7 @@ module L2meter
 
     def transform_log_args(*args)
       params = Hash === args.last ? args.pop : {}
-      args = args.map { |key| [ key, true ] }.to_h
+      args = args.compact.map { |key| [ key, true ] }.to_h
       args.merge(params)
     end
 
@@ -152,7 +152,6 @@ module L2meter
 
     def execute_with_elapsed
       time_at_start = Time.now
-      caught_exception = nil
       [ yield, nil, Time.now - time_at_start ]
     rescue Exception => exception
       [ nil, exception, Time.now - time_at_start ]

data/lib/l2meter/thread_safe.rb

@@ -1,3 +1,5 @@
+require "forwardable"
+
 module L2meter
   # This class is a wrapper around Emitter that makes sure that we have a
   # completely separate clone of Emitter per thread running. It doesn't truly

data/lib/l2meter/version.rb

@@ -1,3 +1,3 @@
 module L2meter
-  VERSION = "0.2.2".freeze
+  VERSION = "0.2.3".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: l2meter
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - Pavel Pravosud
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-11-06 00:00:00.000000000 Z
+date: 2016-02-17 00:00:00.000000000 Z
 dependencies: []
 description: 
 email:
@@ -45,7 +45,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5.1
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: L2met friendly log formatter