Aliaksandr Valialkin

This issue has been resolved in the latest releases of vmagent as mentioned above. Closing it then. @sushovan23 , feel free re-opening it or creating new one if it isn't...

See the related comments at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3521#discussion_r1055919431 and https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3521#discussion_r1055916058 . Summary: * It is ok to round the step value to milliseconds as it was before. * It would be great...

See also the related bug - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3529

FYI, all the comments mentioned at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3510#issuecomment-1364368482 have been addressed by https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3561

`i386` binaries for `vmagent`, `vmalert`, `vmauth`, `vmbackup` and `vmrestore` will be published at [releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases) in the next release.

Binaries for `GOARCH=386` are available at the [releases pages](https://github.com/VictoriaMetrics/VictoriaMetrics/releases) starting from `v1.87.0`. Closing the feature request as done.

@Loori-R , thanks!

FYI, this pull request has been included in [v1.87.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases)

[vmui](https://docs.victoriametrics.com/#vmui) provides an option for filling gaps on graphs starting from [v1.99.0](https://docs.victoriametrics.com/changelog/). Closing the feature request as done.

FYI, the commit 5d66ee88bdb2bbab6419a2854a130c8838998923 removes checking for the `-search.maxUniqueTimeseries` limit at [`/api/v1/labels`](https://docs.victoriametrics.com/url-examples/#apiv1labels) and [`/api/v1/label/.../values`](https://docs.victoriametrics.com/url-examples/#apiv1labelvalues) handlers. This should prevent from returning `the number of matching timeseries exceeds ...` errors in default...