Aliaksandr Valialkin

This issue can be related to https://github.com/golang/go/issues/37506 and https://github.com/golang/go/issues/37688

`vmagent` uses `cgo` only for compressing the last response for the scraped targets with the help of [gozstd](https://github.com/valyala/gozstd) package: https://github.com/VictoriaMetrics/VictoriaMetrics/blob/a6bd442ef9b8f93e40718af3ab45ddafb275f9d6/lib/promscrape/scrapework.go#L236-L256 The `gozstd` package is used actively by other VictoriaMetrics components...

VictoriaMetrics prioritizes data ingestion over queries when it has no enough resources (CPU and disk IO) for processing the current workload. This strategy works better than prioritizing queries over data...

@f41gh7 , could you look into this issue?

There is a workaround - to set up three-level architecture: ``` ------------------------ | vmselect_for_cluster1 | vmselect_middle1 -> | cluster pair1 | | vmselect_for_cluster2 | ------------------------ vmselect_top -> ------------------------ | vmselect_for_cluster1...

FYI, vmalert supports various authorization options for notifiers starting from [v1.82.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases) - see [these docs](https://docs.victoriametrics.com/vmalert.html#notifier-configuration-file).

@foreverm10 , kindly ping regarding the missing test case for the fixed issue

Thanks!

Try using `sum(sum_over_time(...))` instead of `sum(...)` request. The `sum(...)` selects a single data point per each matching time series per `step` interval and then calculates the sum of the selected...

`vmalert` doesn't provide the ability to create and run unit tests for alerting rules as `promtool test rules` [does](https://prometheus.io/docs/prometheus/latest/configuration/unit_testing_rules/). @hagen1778 , could you look into this feature request? It can...