rails_performance 1.0.5 → 1.0.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 437c85fdb48db55caa5da3b41a7b0344d05e27094637cca6f3e8f28f8a15d284
-  data.tar.gz: c4bf8df35605e2cef8de589be79cde872d1a5d5210883140855eb0cf877562d7
+  metadata.gz: ea4ad2cf70bd1a77a745bb88a435280cbd8eb900fb2744eb1a968c4892b526e3
+  data.tar.gz: a51363668bf96e043bd09fff2c20921982aabbcd04b5e94f506ed717b2812a0a
 SHA512:
-  metadata.gz: e54cd14676bde4b86de76a1cc73b482f51dfa9cd7529a658b70bec638e7f0d7eae1af22d60d00e959fbfbd4f3912cce2f6a5c545e8358c949bd0ba0c844e633e
-  data.tar.gz: 7c459ccf377434021fc0d2a4348e95e49ea9ef4e741cc7d768e8f9185121bf7fe36c0cd0b6475aa03fd208cb518f764467880542eb38d994baa8484810e5074f
+  metadata.gz: 2c6323e3c518c12473f4f67c9cc30fb986e6391613b066901f156090a6917a085cf561931d33e0d8e4d6538beee538962b1fd9d48a02883a028178e1598d1b9e
+  data.tar.gz: b098bd3cfd4375250eb7acb4492a486ef1ce5a676df778e9a0bcd25a421ff860a4d2355f8704c3260b02d36e66d11e67a2767dbfb80b3bfbf9497b43116f93b6

data/README.md

@@ -135,6 +135,13 @@ Rails.application.routes.draw do
 end
 ```
 
+### Custom data
+
+You need to configure `config.custom_data_proc`. And you can capture current_user, HTTP User Agent, etc. This proc is executed inside middleware, and you have access to Rack "env".
+
+![Custom Data](docs/custom_data.png)
+
+
 ### Custom events
 
 ```ruby

data/lib/rails_performance/version.rb

@@ -1,4 +1,4 @@
 module RailsPerformance
-  VERSION = '1.0.5'
+  VERSION = '1.0.5.1'
   SCHEMA  = '1.0.1'
 end

data/lib/rails_performance.rb

@@ -79,7 +79,7 @@ module RailsPerformance
 
   # add custom payload to the request
   mattr_accessor :custom_data_proc
-  @@custom_data_proc = []
+  @@custom_data_proc = nil
 
   def RailsPerformance.setup
     yield(self)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails_performance
 version: !ruby/object:Gem::Version
-  version: 1.0.5
+  version: 1.0.5.1
 platform: ruby
 authors:
 - Igor Kasyanchuk