Aliaksandr Valialkin

Results 630 comments of Aliaksandr Valialkin

FYI, the compatibility with AWS Firehose should be fixed in the commit 509df44d03631a863fab00e202a6449c19d784e1

FYI, the `-opentelemetry.usePrometheusNaming` flag has been introduced in the commit fb42380ef374c394053b4cc4f2b083ed4afc7d09 . If this flag is set, then VictoriaMetrics automatically converts metric names and label names into Prometheus-compatible names for...

FYI, [vmagent](https://docs.victoriametrics.com/vmagent/) and [single-node VictoriaMetrics](https://docs.victoriametrics.com/) properly return responses to Amazon Firehose starting from [v1.100.0](https://docs.victoriametrics.com/changelog/). They also support the `-opentelemetry.usePrometheusNaming` command-line flag starting from `v1.100.0` release.

The [count_values_over_time](https://docs.victoriametrics.com/MetricsQL.html#count_values_over_time) function has been added in the commit f7c3dee1c3808ea298fa3ff621069432e0717d83 . This commit will be included in the next release. In the mean time it is possible to test this...

[`count_values_over_time`](https://docs.victoriametrics.com/MetricsQL.html#count_values_over_time) function has been added in [VictoriaMetrics v1.99.0 release](https://docs.victoriametrics.com/changelog/). Closing the feature request as done.

VictoriaMetrics should export timestamps with millisecond precision if `__timestamp__:rfc3339` format option is passed to [/api/v1/export/csv](https://docs.victoriametrics.com/#how-to-export-csv-data), starting from [v1.99.0](https://docs.victoriametrics.com/changelog/). Closing the issue as resolved.

FYI, this pull request has been included in [v1.100.0](https://docs.victoriametrics.com/changelog/).

FYI, the fix for this issue has been included in [v1.93.13 LTS release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.13).

FYI, the fix for this issue has been included in [v1.97.3 LTS release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.3).

The fix for this issue has been included in [v1.99.0 release](https://docs.victoriametrics.com/changelog/). Closing the issue as fixed.