Mechiel Lukkien 3620d6f05e initialize metric mox_panic_total with 0, so the alerting rule also catches the first panic for a label ... increase() and rate() don't seem to assume a previous value of 0 when a vector gets a first value for a label. you would think that an increase() on a first-value mox_panic_total{"..."}=1 would return 1, and similar for rate(), but that doesn't appear to be the behaviour. so we just explicitly initialize the count to 0 for each possible label value. mox has more vector metrics, but panics feels like the most important, and it's too much code to initialize them all, for all combinations of label values. there is probably a better way that fixes this for all cases...		2023-09-15 16:47:17 +02:00
..
dkim.go	initialize metric mox_panic_total with 0, so the alerting rule also catches the first panic for a label	2023-09-15 16:47:17 +02:00
dkim_test.go	mox!	2023-01-30 14:27:06 +01:00
fuzz_test.go	mox!	2023-01-30 14:27:06 +01:00
parser.go	add pedantic mode (used by localserve) that refuses some behaviour that is invalid according to specifications and that we normally accept for compatibility	2023-03-12 15:16:01 +01:00
policy.go	mox!	2023-01-30 14:27:06 +01:00
sig.go	in dkim-signature header, allow FWS anywhere in "z=" (copied headers), and prevent panic in cli command "mox dkim verify" when a dkim-signature cannot be parsed	2023-02-03 13:29:47 +01:00
sig_test.go	mox!	2023-01-30 14:27:06 +01:00
txt.go	mox!	2023-01-30 14:27:06 +01:00
txt_test.go	mox!	2023-01-30 14:27:06 +01:00