VictoriaMetrics/app/vmalert/remotewrite
Roman Khavronenko 0204ce942d
Some checks are pending
build / Build (push) Waiting to run
CodeQL Go / Analyze (push) Waiting to run
main / lint (push) Waiting to run
main / test (test-full) (push) Blocked by required conditions
main / test (test-full-386) (push) Blocked by required conditions
main / test (test-pure) (push) Blocked by required conditions
publish-docs / Build (push) Waiting to run
app/vmalert: update -remoteWrite.concurrency and -remoteWrite.flushInterval (#7272)
Auto-adjust `-remoteWrite.concurrency` cmd-line flags with the number of
available CPU cores in the same way as vmagent does. With this change
the default behavior of vmalert in high-loaded installation should
become more resilient. This change also reduces
`-remoteWrite.flushInterval` from `5s` to `2s` to provide better data
freshness.


---------
Signed-off-by: hagen1778 <roman@victoriametrics.com>
Co-authored-by: Nikolay <nik@victoriametrics.com>
2024-10-22 14:43:55 +02:00
..
client_test.go app/vmalert: switch from table-driven tests to f-tests 2024-07-12 22:41:11 +02:00
client.go app/vmalert: update -remoteWrite.concurrency and -remoteWrite.flushInterval (#7272) 2024-10-22 14:43:55 +02:00
debug_client_test.go vmalert-tool: implement unittest (#4789) 2023-10-13 13:54:33 +02:00
debug_client.go lib/httputils: parse URL before creating HTTP transport (#6820) 2024-08-16 11:32:04 +02:00
init_test.go Vmalert tests (#3975) 2023-03-17 15:57:24 +01:00
init.go app/vmalert: update -remoteWrite.concurrency and -remoteWrite.flushInterval (#7272) 2024-10-22 14:43:55 +02:00
remotewrite.go app/vmalert: follow-up bc37b279aa 2024-06-20 15:12:53 +02:00