Rule testing language

[Silas Snider]

I just noticed the language you use for testing promql internally (github.com/prometheus/prometheus/promql/test.go). Is it appropriate to write some wrapper code to turn this into a general-purpose rule/alert testing tool, or does it have known issues? I've been hurting for one for a while.

[Fabian Reinartz]

Having it as a base for that was and still is the intention.

Essentially it is on our backlog for a while now. What's blocking it is not so much implementation but specification. The syntax for evaluation is something that strongly bothers me. Specifying time (ranges) is fine for the current testing but not suitable for a more general purpose language. Especially as promtool should eventually replace prometheus_cli and the should use the same language for that. The evaluation syntax of the prometheus_cli is not an optimal reference solution to adapt.

It is absolutely on our roadmap (should probably be added to the actual one on the website) but without ETA.

Implementation-wise it is likely worth it to drag the parsing into PromQL entirely.

If you are interested in contributing to push the whole issue forward (through further discussion, suggestions, or coding), we will support you as good as we can in all areas. The whole matter probably just needs a little kick-start.

On Fri, Aug 7, 2015 at 7:02 PM Silas Snider <swsn...@gmail.com> wrote:

I just noticed the language you use for testing promql internally (github.com/prometheus/prometheus/promql/test.go). Is it appropriate to write some wrapper code to turn this into a general-purpose rule/alert testing tool, or does it have known issues? I've been hurting for one for a while.

--
You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Silas Snider]

Thanks for the info -- I'll hang back for right now because I'm also pretty busy :). I might be able to help out in a bit though -- we'll see.