Skip to content

Commit 9a6fc2d

Browse files
committed
DOC: config: add missing glitch_{cnt,rate} data types
When glitch_cnt and glitch_rate data types were implemented in c9c6b68 ("MEDIUM: stick-tables: add a new stored type for glitch_cnt and glitch_rate"), the data types list for "stick-table" keyword documentation was overlooked. This was reported by Nick Ramirez. It should be backported in 3.0 with c9c6b68.
1 parent 3ecca21 commit 9a6fc2d

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

doc/configuration.txt

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12953,6 +12953,21 @@ stick-table type {ip | integer | string [len <length>] | binary [len <length>]}
1295312953
smoothed with "option contstats" though this is not perfect yet. Use of
1295412954
byte_out_cnt is recommended for better fairness.
1295512955

12956+
- glitch_cnt : front glitches count. It is a positive 32-bit integer which
12957+
counts the cumulative number of glitches reported on a front connection.
12958+
Glitches correspond to either unusual or unexpected actions (protocol-
12959+
wise) from the client that could indicate a badly defective client or
12960+
possibly an attacker. As such, this counter can help in order to decide
12961+
how to act with them in such case.
12962+
12963+
- glitch_rate(<period>) : frequency counter (takes 12 bytes). It takes an
12964+
integer parameter <period> which indicates in milliseconds the length of
12965+
the period over which the average is measured. It reports the average
12966+
front glitches rate over that period. It may be used to detect defective
12967+
clients or potential attackers that perform uncommon or unexpected
12968+
actions from a protocol point of view, provided that HAProxy flagged them
12969+
them as such.
12970+
1295612971
There is only one stick-table per proxy. At the moment of writing this doc,
1295712972
it does not seem useful to have multiple tables per proxy. If this happens
1295812973
to be required, simply create a dummy backend with a stick-table in it and

0 commit comments

Comments
 (0)