VictoriaMetrics/vendor
Aliaksandr Valialkin be31bdc88c
app/vmselect/promql: recommend to use (a op b) keep_metric_names instead of a op b keep_metric_names
The `a op b keep_metric_names` is ambigouos to `a op (b keep_metric_names)` when `b` is a transform or rollup function.
For example, `a + rate(b) keep_metric_names`. So it is better to use more clear syntax: `(a op b) keep_metric_names`

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3710
2023-07-16 23:46:34 -07:00
..
cloud.google.com/go vendor: run make vendor-update 2023-07-07 00:04:32 -07:00
github.com app/vmselect/promql: recommend to use (a op b) keep_metric_names instead of a op b keep_metric_names 2023-07-16 23:46:34 -07:00
go.opencensus.io vendor: make vendor-update 2022-11-05 10:34:35 +02:00
go.opentelemetry.io vendor: run make vendor-update 2023-07-07 00:04:32 -07:00
go.uber.org vendor: make vendor-update 2023-05-09 23:13:50 -07:00
golang.org/x vendor: run make vendor-update 2023-07-07 00:04:32 -07:00
google.golang.org vendor: run make vendor-update 2023-07-07 00:04:32 -07:00
gopkg.in vmctl: support of the remote read protocol (#3232) 2022-11-29 22:53:28 +01:00
modules.txt app/vmselect/promql: recommend to use (a op b) keep_metric_names instead of a op b keep_metric_names 2023-07-16 23:46:34 -07:00