This is what is the problem with such compatibility tests... they tend to test full power of the language while you really may use quite small subset in your application, as such even solution which is "20% compatible" may well meet all your application needs.
I remember in its early days MySQL had pretty poor SQL support (if you think about full standard) which did not prevent it from having huge success.
Or more recent example ClickHouse which I think similar to VictoriaMetrics as it does not fully implement SQL, but also adds many convenient extensions which are not part of the standard.
Chances are if you chose VictoriaMetrics you will find a lot more utility in advanced features of MetricsQL than you loose from exact compatibility with PromQL
The majority of failed tests for VictoriaMetrics cannot be "fixed" due to deliberate choice made when designing MetricsQL: to rethink and to fix the most annoying and confusing parts of PromQL, while providing drop-in PromQL replacement for the majority of practical cases. See more details at https://victoriametrics.github.io/MetricsQL.html .
[+] [-] shitloadofbooks|5 years ago|reply
This summary makes it seem like Victoria Metrics is barely compatible with Prometheus, but that can't be further from the truth in practice.
[+] [-] PeterZaitsev|5 years ago|reply
I remember in its early days MySQL had pretty poor SQL support (if you think about full standard) which did not prevent it from having huge success.
Or more recent example ClickHouse which I think similar to VictoriaMetrics as it does not fully implement SQL, but also adds many convenient extensions which are not part of the standard.
Chances are if you chose VictoriaMetrics you will find a lot more utility in advanced features of MetricsQL than you loose from exact compatibility with PromQL
[+] [-] EdwardDiego|5 years ago|reply
We're currently running Prometheus + Thanos, and high cardinality timeseries are a real issue, which Victoria claims to be good at.
[+] [-] pointestimate|5 years ago|reply
How do you include that in a CI/CD environment with regression testing?
[+] [-] benraskin92|5 years ago|reply
[+] [-] jrv|5 years ago|reply
[+] [-] valyala|5 years ago|reply
These tests are great, because they spotted a few minor bugs in our PromQL implementation and these bugs were fixed quickly. See https://victoriametrics.github.io/CHANGELOG.html .
The majority of failed tests for VictoriaMetrics cannot be "fixed" due to deliberate choice made when designing MetricsQL: to rethink and to fix the most annoying and confusing parts of PromQL, while providing drop-in PromQL replacement for the majority of practical cases. See more details at https://victoriametrics.github.io/MetricsQL.html .
[+] [-] harkishen|5 years ago|reply
[deleted]