|
|
|
|
|
|
by mshekow
1215 days ago
|
|
|
It took me a while to understand what your tool is doing. It looks like an abstraction layer for concrete monitoring/alerting solutions. What confuses me is: - You introduce Keep like this "Think of Keep as Prometheus Alertmanager but for all observability tools", but then there is no Alertmanager provider. Is this planned? - You mention that you support the 3 hyperscaler clouds (AWS, ...), yet I do not see any examples or code that backs this up - You mention that Keep can be used to _test_ alerts. How? Examples? Otherwise make it clear that you _plan_ that Keep can do this at some point. In general though it looks very interesting :). |
|
|
Regarding your questions:
- Working on the Grafana/Prometheus provider and it'll be shipped in <1 week
- AWS and GCP are in final tests, we thought we could release that before it gets any traction ^^" anyway, PRs will be available in <2 days
- There are two things here: 1. You can simply test if your alert "triggers" just by running the CLI with the --verbose and --alerts-file 2. We plan on adding tests that will both allow you to "mock" the alert to see that it acts as you planned & source control integrated (e.g. a GitHub action) tests that will tell you when a code change breaks your alerts
anyway, if you have any other questions/thoughts, feel free to open an issue and we'll address it right away