imprint 1.4.1 → 1.4.2

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -121,7 +121,7 @@ First query to find a group of requests you are particularly interested in, perh
121
121
 
122
122
  source="app_name" error status=500
123
123
 
124
- From the results find a specific request that caused the error and use the trace_id to dig in futher, by crafting a query with the trace_id.
124
+ From the results find a specific request that caused the error and use the trace_id to dig in further, by crafting a query with the trace_id.
125
125
 
126
126
  Find all log lines in a particular app related to a single request:
127
127
 
@@ -147,7 +147,7 @@ end
147
147
  Resque.enqueue(klazz, options)
148
148
  ```
149
149
 
150
- Once it is on the queue, I want to log the ID but remove it from the params as some jobs work direclty with an expected set of params.
150
+ Once it is on the queue, I want to log the ID but remove it from the params as some jobs work directly with an expected set of params.
151
151
 
152
152
  ```ruby
153
153
  def before_perform(*args)
@@ -303,7 +303,7 @@ initiating event.
303
303
 
304
304
  ## Notes / TODO
305
305
 
306
- Looking at ZipKin, it tries to accomplish many of the same goals as Imprint. I think it would make sence to support the same headers and format so they could be compatible. Although the ZipKin service tracing isn't as useful to me as the full detailed splunk / elastic search logs.
306
+ Looking at ZipKin, it tries to accomplish many of the same goals as Imprint. I think it would make sense to support the same headers and format so they could be compatible. Although the ZipKin service tracing isn't as useful to me as the full detailed Splunk/ElasticSearch logs.
307
307
 
308
308
  * [ZipKin intro / docs](http://twitter.github.io/zipkin/index.html)
309
309
  * [Railsconf ZipKin intro: Distributed Request Tracing](http://www.confreaks.com/videos/3326-railsconf-distributed-request-tracing) by [Kenneth Hoxworth (@hoxworth)](https://twitter.com/hoxworth)
data/changelog.txt ADDED
@@ -0,0 +1,5 @@
1
+
2
+
3
+ * Jan 7, 2015: move the default trace_id from -1 to "-1" this breaks some apps test integration but is unlikely to have real world effects. Bumped to Version 1.4.2
4
+
5
+ * before Jan 7 2015, see git history no change log existed then
@@ -3,7 +3,7 @@ module Imprint
3
3
  TRACER_HEADER = 'HTTP_IMPRINTID'
4
4
  TRACER_KEY = 'IMPRINTID'
5
5
  RAILS_REQUEST_ID = "action_dispatch.request_id"
6
- TRACE_ID_DEFAULT = -1
6
+ TRACE_ID_DEFAULT = "-1"
7
7
 
8
8
  TRACE_CHARS = [('a'..'z'), ('A'..'Z')].map { |i| i.to_a }.flatten
9
9
 
@@ -1,3 +1,3 @@
1
1
  module Imprint
2
- VERSION = "1.4.1"
2
+ VERSION = "1.4.2"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: imprint
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.4.1
4
+ version: 1.4.2
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2014-10-13 00:00:00.000000000 Z
12
+ date: 2015-01-29 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: bundler
@@ -105,6 +105,7 @@ files:
105
105
  - LICENSE.txt
106
106
  - README.md
107
107
  - Rakefile
108
+ - changelog.txt
108
109
  - imprint.gemspec
109
110
  - lib/imprint.rb
110
111
  - lib/imprint/log_helpers.rb
@@ -131,7 +132,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
131
132
  version: '0'
132
133
  segments:
133
134
  - 0
134
- hash: 937198868224264989
135
+ hash: -2434163442242259334
135
136
  required_rubygems_version: !ruby/object:Gem::Requirement
136
137
  none: false
137
138
  requirements:
@@ -140,7 +141,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
140
141
  version: '0'
141
142
  segments:
142
143
  - 0
143
- hash: 937198868224264989
144
+ hash: -2434163442242259334
144
145
  requirements: []
145
146
  rubyforge_project:
146
147
  rubygems_version: 1.8.23