Pint supports VictorMetrics

[rakeshpb90]

I would like to know whether Pint supports Victoriametrics. I'm receiving a 400 response code for the following API's /api/v1/status/config and /api/v1/status/flags

[wonderg]

It seems the challenge with Pint and VictoriaMetrics originates from Pint's use of the Prometheus-specific endpoint /api/v1/status/config in internal/promapi/config.go, which VictoriaMetrics doesn't support. While I'm not a Go developer and cannot guarantee a solution, a potential workaround might involve mapping the required configuration details (like ExternalLabels, ScrapeInterval, ScrapeTimeout, and EvaluationInterval) from equivalent VictoriaMetrics and VMAlert settings. This suggestion is speculative and would need further exploration to implement effectively.

[andrew-shevchyk]

I'm working on research how to implement VM support in pint (but I'm not Go developer either so using this opportunity to get familiar with it), I mocked responses from Prom server but faced another issue - VictoriaMetrics extends PromQL with additional functions so if an alerting rule uses them then it can't be parsed and the validation fails.
I'm looking into using VM library for parsing but not sure if it would be feasible to adapt due to significant differences in structures comparing to PromQL parser

[wonderg]

Yes, you are right about MetricsQL, but it is probably worth starting with PromQL support only, because the reality is that only a few products use MetricsQL, while VictoriaMetrics is quite popular as a long term storage for metrics. So it is good to have support for MetricsQL, but not necessary, and in most cases PromQL support should be enough.

[antoinedeschenes]

Regarding compatibility, I've successfully disabled pint's promql/syntax check and combined vmalert-prod -dryRun -rule 'rulefile.yaml' to handle expr linting.

I've also used yq to remove VM-only fields in the rules specification (ex. group-level labels, concurrency, etc.)

Now where I'm hitting problems is that vmalert supports additional template values and functions over Prometheus in alert labels and annotations, and linting these expressions isn't covered by vmalert's validation checks.