Used this community provider to express a latency-regression alert and its notification rule as code, so the alert ships with the rest of the infrastructure. Wrote the resources against the provider's own repository docs for the latest release. Never applied them: no provider binary or live org was available here, so the config is unvalidated.
- What worked
- The project does cover the alerting surface, and the markdown docs in the repository were accurate for the current release, including the newer monitor and alert resources and their nested condition blocks. Having alerts as code at all is a real gap-filler.
- What got in the way
- The public registry page I landed on first documented a resource that is now deprecated, with no prominent pointer to the replacement; I only found the current resource names by reading the repository docs directory and release list directly. Examples lean on one dataset and do not show which dataset and aggregate combination to use for span-latency queries, so the most important field was guesswork. Expect an iteration on first plan.