@@ -25,7 +25,7 @@ Documentation written by Tom Zanussi
2525
2626 hist:keys=<field1[,field2,...]>[:values=<field1[,field2,...]>]
2727 [:sort=<field1[,field2,...]>][:size=#entries][:pause][:continue]
28- [:clear][:name=histname1][:<handler>.<action>] [if <filter>]
28+ [:clear][:name=histname1][:nohitcount][: <handler>.<action>] [if <filter>]
2929
3030 When a matching event is hit, an entry is added to a hash table
3131 using the key(s) and value(s) named. Keys and values correspond to
@@ -79,6 +79,8 @@ Documentation written by Tom Zanussi
7979 .log2 display log2 value rather than raw number
8080 .buckets=size display grouping of values rather than raw number
8181 .usecs display a common_timestamp in microseconds
82+ .percent display a number of percentage value
83+ .graph display a bar-graph of a value
8284 ============= =================================================
8385
8486 Note that in general the semantics of a given field aren't
@@ -137,6 +139,12 @@ Documentation written by Tom Zanussi
137139 existing trigger, rather than via the '>' operator, which will cause
138140 the trigger to be removed through truncation.
139141
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+
140148- enable_hist/disable_hist
141149
142150 The enable_hist and disable_hist triggers can be used to have one
0 commit comments