Aliaksandr Valialkin

This sounds good!

FYI, the MetricsQL parser has been moved to a separate repository with its own release schedule - https://github.com/VictoriaMetrics/metricsql . This should significantly simplify its' integration into third-party projects such as...

The idea looks interesting. But it is unclear how to configure prepared statements in simple and maintainable way. @winem , could you propose something in this direction?

This is possible in general case, but it may be hard to implement, since chproxy uses standard [net/http](https://golang.org/pkg/net/http/) from Go for http client and server. They don't provide streaming headers'...

I'm unsure this helper function is better than `fmt.Sprintf()` from readability and maintainability points of view. IMHO, `fmt.Sprintf("metric_name{label1=%q, ... , labelN=%q}", labelValue1, ..., labelValueN)` is easier to read, understand and...

> Indeed, scanning through the code, I've not found labels sorting, looks like foo{bar=val,baz=ue} isn't the same as foo{baz=ue,bar=val} Yes, this looks like a low-priority issue, which may be addressed...

It would be great to have performance numbers and/or cpu profiles obtained from highly loaded systems where metrics sampling could result in better performance.

As I know, the `vmbackup` ma run as a sidecar in the same pod as single-node VictoriaMetrics or `vmstorage` component in cluster version. cc'ing @tenmozes for more input

There are plans to add `statsd`-like service into [vmagent](https://victoriametrics.github.io/vmagent.html) - see https://github.com/VictoriaMetrics/VictoriaMetrics/issues/206 .

@shedimon , thanks for the feature request! The proposed `metrics_push_*` metrics are published starting from [v1.21.0](https://github.com/VictoriaMetrics/metrics/tree/v1.21.0) - see e9b4bb1534f39252df9b249495c3211ceba204db for implementation details. As for the proposed change for `extraLabels` arg,...