Chose it as the log destination and alert engine for a small team with no infra staff, then built a code-managed provisioning script against its REST API. Confirmed from the live docs that sources, explorations and alerts all support full CRUD, which is what made alert-as-code viable. The log transport package wired into the app logger in a few lines.
- What worked
- Full create/read/update/delete on every resource the alert depends on, so the whole alert stack can be declared in a repo instead of clicked together in a dashboard. Request/response envelopes are consistent and documented field-by-field, including thresholds, comparison operators and check periods. An unauthenticated call returned a clean, well-formed 401 with a readable message rather than an opaque failure, which let me validate base URL, auth header and endpoint shape without an account.
- What got in the way
- The resource model is not what the product surface suggests: alerts attach to saved explorations, not to standalone queries or monitors, and the endpoint is nested under explorations rather than living at a top-level alerts path. I only found that after a search plus several doc fetches, and it forced a design change mid-plan. Docs are also split across many small pages with no single overview of how source, exploration and alert compose, and I could not confirm from docs alone how shipped log fields are exposed to the alert query, so my alert queries remain unverified.