Aliaksandr Valialkin

FYI, VictoriaMetrics and vmagent sanitize metric names by default when they are ingested via [DataDog protocol](https://docs.victoriametrics.com/#how-to-send-data-from-datadog-agent) starting from [v1.82.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases). It the ingested metric names shouldn't be sanitized, then `-datadog.sanitizeMetricName=false` command-line...

The next release of VictoriaMetrics will support `timezone_offset()` function, which returns the offset in seconds for the given timezone. For example `timezone_offset("Europe/Lisbon")` usually returns 3600. See the full list of...

The `timezone_offset()` function is available starting from [v1.60.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases). See [MetricsQL docs](https://docs.victoriametrics.com/MetricsQL.html) for details.

@skeagy , thanks for the pull request! The commit https://github.com/VictoriaMetrics/VictoriaMetrics/commit/41f8c2987ddc04bf1bf619937c72ac9dd7af68a9 uses slightly different approach for allowing whitespace in Graphite tags without the need to fall back to non-standard escaping or...

@nightirbis95 , it is likely there were data parts at `/data/big/2022_07` with samples, which fit the specified `-retentionPeriod=3w` . In this case VictoriaMetrics cannot delete these parts until all the...

There are no plans for implementing automatic data rebalancing, since it has the following pitfalls: - It can eat all the resources - network bandwidth, disk IO bandwidth, CPUs -...

> Do you mean that only the new vmstorage node will need to be stopped or should the cluster be in a locked state (no inserts). I guess that since...

@hagen1778 , thanks for the bugfix!

The solution with [aggregate function](https://docs.victoriametrics.com/MetricsQL.html#aggregate-functions) is the best one. If time series with different label names aren't intersected, and they have common `id` label, then the following query should merge...

> Is there also a way to use aggr_over_time with this approach? I was using max_over_time, avg_over_time and min_over_time within aggr_over_time, but instead of 3 metrics it returns 6 because...