> You continue to claim that VictoriaMetrics is backwards-compatible with Prometheus and only include a side-note that it actually is not in all cases * There

> You continue to claim that VictoriaMetrics is backwards-compatible with Prometheus and only include a side-note that it actually is not in all cases * There are a few controversial cases where VictoriaMetrics' implementation for PromQL intentionally diverges from the original implementation in Prometheus. This discrepancy is needed because VictoriaMetrics tries hard to make PromQL more user-friendly at edge cases, which aren't solved for a long time on Prometheus side [1]. * Of course, there may be non-intentional discrepancies in PromQL implementation for VictoriaMetrics, because it is implemented from scratch without using Prometheus data model and source code. Such discrepancies are usually fixed as soon as users report about them. > It's not about competition (we welcome and love that from all sides) I see. Facts mentioned in this topic shows the real love :) [1] https://github.com/prometheus/prometheus/issues/3746 https://github.com/prometheus/prometheus/issues/3746