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
..
account.go	add package-level comments for webadmin and webaccount	2023-09-15 16:01:23 +02:00
account.html	implement message threading in backend and webmail	2023-09-13 15:44:57 +02:00
account_test.go	implement message threading in backend and webmail	2023-09-13 15:44:57 +02:00
accountapi.json	add flag to ruleset that indicates a message is forwarded, slightly modifying how junk analysis is done	2023-08-09 22:31:37 +02:00
import.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