blob: b2c0e8d9c372c89eb9d128fce71e81ba036bae39 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
# Ensure that Riak is running. template: riak_last_collected_secs
template: riakkv_last_collected_secs
on: riak.kv.throughput
class: Database
component: Riak KV
type: Latency
calc: $now - $last_collected_t
units: seconds ago
every: 10s
warn: $this > (($status >= $WARNING) ? ($update_every) : ( 5 * $update_every))
crit: $this > (($status == $CRITICAL) ? ($update_every) : (60 * $update_every))
delay: down 5m multiplier 1.5 max 1h
info: number of seconds since the last successful data collection
to: dba
# Warn if a list keys operation is running.
template: riakkv_list_keys_active
on: riak.core.fsm_active
class: Database
component: Riak KV
type: Utilization
calc: $list_fsm_active
units: state machines
every: 10s
warn: $list_fsm_active > 0
info: number of currently running list keys finite state machines
to: dba
## Timing healthchecks
# KV GET
template: riakkv_1h_kv_get_mean_latency
on: riak.kv.latency.get
class: Database
component: Riak KV
type: Latency
calc: $node_get_fsm_time_mean
lookup: average -1h unaligned of time
every: 30s
units: ms
info: average time between reception of client GET request and \
subsequent response to client over the last hour
template: riakkv_kv_get_slow
on: riak.kv.latency.get
class: Database
component: Riak KV
type: Latency
calc: $mean
lookup: average -3m unaligned of time
units: ms
every: 10s
warn: ($this > ($riakkv_1h_kv_get_mean_latency * 2) )
crit: ($this > ($riakkv_1h_kv_get_mean_latency * 3) )
info: average time between reception of client GET request and \
subsequent response to the client over the last 3 minutes, \
compared to the average over the last hour
delay: down 5m multiplier 1.5 max 1h
to: dba
# KV PUT
template: riakkv_1h_kv_put_mean_latency
on: riak.kv.latency.put
class: Database
component: Riak KV
type: Latency
calc: $node_put_fsm_time_mean
lookup: average -1h unaligned of time
every: 30s
units: ms
info: average time between reception of client PUT request and \
subsequent response to the client over the last hour
template: riakkv_kv_put_slow
on: riak.kv.latency.put
class: Database
component: Riak KV
type: Latency
calc: $mean
lookup: average -3m unaligned of time
units: ms
every: 10s
warn: ($this > ($riakkv_1h_kv_put_mean_latency * 2) )
crit: ($this > ($riakkv_1h_kv_put_mean_latency * 3) )
info: average time between reception of client PUT request and \
subsequent response to the client over the last 3 minutes, \
compared to the average over the last hour
delay: down 5m multiplier 1.5 max 1h
to: dba
## VM healthchecks
# Default Erlang VM process limit: 262144
# On systems observed, this is < 2000, but may grow depending on load.
template: riakkv_vm_high_process_count
on: riak.vm
class: Database
component: Riak KV
type: Utilization
calc: $sys_process_count
units: processes
every: 10s
warn: $this > 10000
crit: $this > 100000
info: number of processes running in the Erlang VM
to: dba
|
