l2meter 0.2.4 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9a603e188a8c1ca88ca691d1dc36acb560d45776
-  data.tar.gz: 3b6b103b4e385beb3b792cd1ab209e13e517be42
+  metadata.gz: 8813cc61c6cf80054b1f532ac952b4a3a8e9bcc1
+  data.tar.gz: bc8267895efdd3544c3bd1309504e0bc2f5d3135
 SHA512:
-  metadata.gz: e431dab04d27159b89a6426f524f0965009e1002936985cdaf1b680bab1a14f444f6e1dfe139f487d9c2f96bf063a28164f5260e83d99ffbcf32ab925f75049e
-  data.tar.gz: 0613c23b01a2f066c9a4c77328e1fe91b0013e8a145f5c9a9c7541966dcdd8fe3bf297ececc737e1e4715e6f3dc44577e62ad4fa5b782254123d457f0a2afa13
+  metadata.gz: befb44d3bb18e708a2c2172036efdb6863688e8cace9f7c94adc4c55b38621f9dfd7b5a5338654b2f35271a4b0265023ace125983c7cf0cb41632d9ea84664af
+  data.tar.gz: e32e10b222b91ae98390f4c730e20d12ce59b3912b3f3ea4105621278d2517aa7ee2f3b2668aa3d2f376228e4793f3168f1392d8e95d03cccbc07f84081567f0

data/README.md

@@ -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 at=start
   raise ArgumentError, \    #
     "something is wrong"    #
 end                         # => doing-work at=exception exception=ArgumentError message="something is wrong" elapsed=1.2345s
@@ -107,12 +107,23 @@ L2meter also allows to append elapsed time to your log messages automatically.
 ```ruby
 Metrics.with_elapsed do
   do_work_step_1
-  log :step_1_done # => step-1-done elapsed=1.2345s
+  Metrics.log :step_1_done # => step-1-done elapsed=1.2345s
   do_work_step_2
-  log :step_2_done # => step-2-done elapsed=2.3456s
+  Metrics.log :step_2_done # => step-2-done elapsed=2.3456s
 end
 ```
 
+There's also a way to batch several calls into a single log line:
+
+```ruby
+Metrics.batch do
+  Metrics.log foo: :bar
+  Metrics.unique :registeration, "user@example.com"
+  Metrics.count :thing, 10
+  Metrics.sample :other_thing, 20
+end # => foo=bar unique#registration=user@example.com count#thing=10 sample#other-thing=20
+```
+
 ### Configuration
 
 L2meter supports configuration. Here's how you can configure things:
@@ -140,7 +151,7 @@ Metrics.log foo: :bar # => app-name=my-app-name foo-bar
 Dynamic context is also supported:
 
 ```ruby
-context.context do
+config.context do
   { request_id: CurrentContext.request_id }
 end
 ```

data/lib/l2meter/emitter.rb

@@ -69,6 +69,13 @@ module L2meter
       self.class.new(configuration: configuration)
     end
 
+    def batch
+      @outputs.push StringIO.new
+      yield
+    ensure
+      emit @outputs.pop.tap(&:rewind).read.split(/\s+/).uniq.join(" ")
+    end
+
     private
 
     def transform_log_args(*args)
@@ -122,9 +129,14 @@ module L2meter
 
       tokens.sort! if configuration.sort?
 
-      output_queue.last.print tokens.join(" ") + "\n"
+      emit tokens.join(" ")
     end
 
+    def emit(text)
+      output_queue.last.puts text
+    end
+
+
     def log_with_prefix(method, key, value, unit: nil)
       key = [configuration.prefix, key, unit].compact * ?.
       log Hash["#{method}##{key}", value]

data/lib/l2meter/thread_safe.rb

@@ -9,6 +9,7 @@ module L2meter
     extend Forwardable
 
     EMITTER_METHODS = %i[
+      batch
       configuration
       context
       count

data/lib/l2meter/version.rb

@@ -1,3 +1,3 @@
 module L2meter
-  VERSION = "0.2.4".freeze
+  VERSION = "0.3.0".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: l2meter
 version: !ruby/object:Gem::Version
-  version: 0.2.4
+  version: 0.3.0
 platform: ruby
 authors:
 - Pavel Pravosud
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-02-17 00:00:00.000000000 Z
+date: 2016-02-24 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.5.1
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: L2met friendly log formatter