@@ -25,7 +25,7 @@ Documentation written by Tom Zanussi
25
25
26
26
hist:keys=<field1[,field2,...]>[:values=<field1[,field2,...]>]
27
27
[:sort=<field1[,field2,...]>][:size=#entries][:pause][:continue]
28
- [:clear][:name=histname1][:<handler>.<action>] [if <filter>]
28
+ [:clear][:name=histname1][:nohitcount][: <handler>.<action>] [if <filter>]
29
29
30
30
When a matching event is hit, an entry is added to a hash table
31
31
using the key(s) and value(s) named. Keys and values correspond to
@@ -79,6 +79,8 @@ Documentation written by Tom Zanussi
79
79
.log2 display log2 value rather than raw number
80
80
.buckets=size display grouping of values rather than raw number
81
81
.usecs display a common_timestamp in microseconds
82
+ .percent display a number of percentage value
83
+ .graph display a bar-graph of a value
82
84
============= =================================================
83
85
84
86
Note that in general the semantics of a given field aren't
@@ -137,6 +139,12 @@ Documentation written by Tom Zanussi
137
139
existing trigger, rather than via the '>' operator, which will cause
138
140
the trigger to be removed through truncation.
139
141
142
+ The 'nohitcount' (or NOHC) parameter will suppress display of
143
+ raw hitcount in the histogram. This option requires at least one
144
+ value field which is not a 'raw hitcount'. For example,
145
+ 'hist:...:vals=hitcount: nohitcount' is rejected, but
146
+ 'hist:...:vals=hitcount.percent: nohitcount' is OK.
147
+
140
148
- enable_hist/disable_hist
141
149
142
150
The enable_hist and disable_hist triggers can be used to have one
0 commit comments