Aliaksandr Valialkin

@f41gh7 , could you look into this feature request?

This might be intended behavior. VictoriaMetrics thinks that time series is active if at least a singe data point exists on a time range equal to the given `step`. Longer...

FYI, VictoriaMetrics and vmagent gains support for Prometheus staleness marks. This should fix the issue with inflated `count()` results. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1526#issuecomment-898323054 .

FYI, VictoriaMetrics and vmagent gained support for Prometheus staleness markers starting from [the release v1.64.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases).

@advancedwebdeveloper , thanks for doing this! It would be great if you could add missing bits needed for building VictoriaMetrics with gollvm. It would be great mentioning that VictoriaMetrics could...

This is interesting idea. It isn't hard to add data exporting in Parquet format according to pre-defined columns for the exported data - `(timeseries_name_plus_tags []string, timestamps []int64, values []float64)`. It...

This is expected behavior - VictoriaMetrics may have incomplete set of values for recent timestamps. So, instead of calculating value on possibly incomplete set of raw samples, it returns previously...

This looks like a bug - [export API](https://docs.victoriametrics.com/#how-to-export-time-series) must return real [raw samples](https://docs.victoriametrics.com/keyconcepts/#raw-samples) stored in the database. The `/api/v1/query?series_selector[d]` is considered as export API, since it returns raw samples -...

As I know, TimescaleDB and MySQL don't provide the ability to export data to remote storage systems. I think it would be better asking Zabbix team to add VictoriaMetics as...

> Wasn't sure if there was anything that could be done on a pull basis rather than push. That's interesting idea - standalone services could be created for pulling metrics...