unicorn_wrangler 0.1.2 → 0.2.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/unicorn_wrangler.rb +1 -1
- data/lib/unicorn_wrangler/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 82e546ee3d77b187e7cac827c3d04cf8c15524f6
|
|
4
|
+
data.tar.gz: c8129c73c35008e431c4ef014ff99b3367b4b252
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 36f6702fe7ae1963cc7ce6b34ff1d4587cfe386f949e410efda4941bdc81f4451ed5872c78d2a80a02d5ff43d135ca035539716be0280fad6c24198f88bf7149
|
|
7
|
+
data.tar.gz: d39351c904a9b848e4cda23a7c30f5e181eba6232b3fb50736f82303c47c22595d8989f57a114f9de0334ef8619411f8f0f57fe33ffacea5ccb449d25caf0f08
|
data/lib/unicorn_wrangler.rb
CHANGED
|
@@ -60,7 +60,7 @@ module UnicornWrangler
|
|
|
60
60
|
# Possible issue: kill_worker is not meant to kill the server pid ... might have strange side effects
|
|
61
61
|
def kill(reason, memory, requests, request_time)
|
|
62
62
|
if @stats
|
|
63
|
-
@stats.increment("#{STATS_NAMESPACE}.
|
|
63
|
+
@stats.increment("#{STATS_NAMESPACE}.killed", tags: ["reason:#{reason}"])
|
|
64
64
|
|
|
65
65
|
@stats.histogram("#{STATS_NAMESPACE}.kill.memory", memory)
|
|
66
66
|
@stats.histogram("#{STATS_NAMESPACE}.kill.total_requests", requests)
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: unicorn_wrangler
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.2.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Michael Grosser
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2017-
|
|
11
|
+
date: 2017-06-01 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
13
|
description:
|
|
14
14
|
email: michael@grosser.it
|