Hello M3DB team,

I hope this email finds you well.

As a part of Prometheus conformance program
<https://github.com/cncf/prometheus-conformance>, we had floated a doc on
"Prometheus Alert-Generator Compliance" many months ago and had finalized
the specification for that (see here
<https://github.com/prometheus/compliance/blob/main/alert_generator/specification.md>
).

The test suite to test the specification is now ready and instructions on
how to run the test suite are present here
<https://github.com/prometheus/compliance/blob/main/alert_generator/README.md>
.

If you wish M3 to be compliant with Prometheus Alert-Generator, please test
your software with the above test suite and report back the results by
replying to this thread (results being the entire log output of the test
run).

If you do need any additional help from the test suite (for example setting
custom headers to some requests), please let me know and I will add those
abilities to the test suite.

Going forward, we would like to automate this process. We ask you to add
your test-suite config template by opening a PR against
prometheus/compliance <https://github.com/prometheus/compliance/> and
create test-m3.yaml in the alert_generator directory. See test-.*.yaml
 files here
<https://github.com/prometheus/compliance/tree/main/alert_generator> for
example. Please also add instructions on how to set up as comments in the
same file.

If you face issues in running the test suite or understanding any error
messages, I am happy to answer your queries.

We plan to publish the results during the third week of May 2022 (during
KubeCon EU).

Thanks,
Ganesh (codesome)
Prometheus team

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-developers/CAERru7PApODSSBn0D33XQED_bnDPhPB2vS3zMgBBfka%2B02uRVQ%40mail.gmail.com.

Reply via email to