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
..
db.go	more logging around smtp and mtasts tls connections	2023-06-04 17:55:55 +02:00
db_test.go	update to latest bstore (with support for an index on a []string: Message.DKIMDomains), and cyclic data types (to be used for Message.Part soon); also adds a context.Context to database operations.	2023-05-22 14:40:36 +02:00
refresh.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
refresh_test.go	update to latest bstore (with support for an index on a []string: Message.DKIMDomains), and cyclic data types (to be used for Message.Part soon); also adds a context.Context to database operations.	2023-05-22 14:40:36 +02:00