4 commits

Author	SHA1	Message	Date
Hui Wang	000a918f38	app/vmalert-tool: print an error message if no rule group is found under 'rule_files' ... Both vmalert and vmalert-tool support multiple `rule_files` and use directory as a file, so it's ok if some files don't contain any rule group. But vmalert-tool should warn the user if no rule group is found in any of the `rule_files`. Related issue: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7663	2024-11-29 10:29:04 +01:00
Hui Wang	0fc1130f47	vmalert-tool: add -external.label and -external.url command-line … (#6766) ... …flags to perform the same as vmalert address https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6735 --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>	2024-08-19 21:29:28 +02:00
Aliaksandr Valialkin	0078399788	app/vmalert: switch from table-driven tests to f-tests ... This makes test code more clear and reduces the number of code lines by 500. This also simplifies debugging tests. See https://itnext.io/f-tests-as-a-replacement-for-table-driven-tests-in-go-8814a8b19e9e While at it, consistently use t.Fatal* instead of t.Error* across tests, since t.Error* requires more boilerplate code, which can result in additional bugs inside tests. While t.Error* allows writing logging errors for the same, this doesn't simplify fixing broken tests most of the time. This is a follow-up for a9525da8a4	2024-07-12 22:41:11 +02:00
Haleygo	dc28196237	vmalert-tool: implement unittest (#4789) ... 1. split package rule under /app/vmalert, expose needed objects 2. add vmalert-tool with unittest subcmd https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2945	2023-10-13 13:54:33 +02:00