Aliaksandr Valialkin

Please consider the migration to [VictoriaLogs](https://docs.victoriametrics.com/victorialogs/). It supports the same log stream concept as Loki, but it is much easier to configure, upgrade and maintain. It doesn't break data storage...

@AndrewChubatiuk , the stream parsing mode must be disabled by default for HTTP-based data ingestion for Influx line protocol, since this is the major source of issues for Telegraf users....

FYI, the [`/select/logsql/stats_query_range`](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-range-stats) endpoint at VictoriaLogs is implemented in the commit [0a40064a6fa64f9d3e3ae60f6f12a9584dce459d](https://github.com/VictoriaMetrics/VictoriaMetrics/commit/0a40064a6fa64f9d3e3ae60f6f12a9584dce459d) . See [these docs](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-range-stats) for details. This endpoint must be used by the VictoriaLogs datasource for building time...

FYI, VictoriaLogs gained support for [`histogram` stats function](https://docs.victoriametrics.com/victorialogs/logsql/#histogram-stats) starting from [v1.6.0-victorialogs release](https://docs.victoriametrics.com/victorialogs/changelog/). This opens the door for heatmaps at VictoriaLogs datasource. For example, the following query to [`/select/logsql/stats_query`](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-stats): ```logsql *...

The proposed structure of the docs looks good. Please take especial care to don't break the existing urls, since they may exist all over the Internet, and they should continue...

The related feature request - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/643

> We should also discourage people from using field:$field_filter syntax if $field_filter is a multi-value variable. I disagree. The most common case is when the `$field_filter` must exactly match one...

Also, I think it shouldn't be any difference with the extrapolation of the `$field_filter` for multi-value and single-value filters, since both filter types must exactly match the selected values. Note...

FYI, the commit https://github.com/VictoriaMetrics/VictoriaMetrics/commit/84d5771b41cef5f8b80acd8c11b8546aadc5b0f7 adds support for `in(*)` filter into VictoriaLogs. This filter is treated as `match all`. This commit will be included in the next release of VictoriaLogs. After...

> I suggest we can update variables parsing in a way that would satisfy the following truth table: The provided table looks mostly OK, except of the following things: -...