New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prometheus Alert-Generator Compliance testing for Thanos #5203
Comments
Added priority as I feel this is important to do in the short-term. |
I am interested in helping implement the test. Right now I can think about two setups:
@codesome Should we choose only one setup or add 2 modes for tests? |
I believe those are 2 modes in which Thanos can run. Are there any fundamental difference in those 2 modes? If there is a difference, then it makes sense to test both, saying Thanos is compliant in both modes. If there is not much difference, then you could choose the one which is easiest to setup and test. (PS: "Alertmanager" here will be the test suite if that was not obvious) |
Thanks @codesome. I see what you meant. If it is for alerts generating stuff then there is no difference I think. |
Does anyone want to do this? Not much time left ((: |
I did it here #5315 - sorry somehow missed this discussion 🙈 Let me know if this makes sense |
I did the mode for receiver, since it makes more sense as the test suites needs to push data and our default receiver is Thanos Receive (: |
As per Prometheus dev mailing list we need to add Thanos config template test suite so Thanos is automatically tested for compatibility over Prometheus APIs.
Thanks @codesome for ping!
Help wanted - deadline for at lease test result - KubeCon
The text was updated successfully, but these errors were encountered: