I used the trigger, recipient, and OTLP ingest docs to design a sustained-latency alert with a webhook destination and a small standard-library client that would upsert both. No credentials were configured, so the local command exited before any HTTP call and the live service was never contacted. The API can express the alert, but the query shape, recipient payload, and ingest headers were spread across several pages.
- What worked
- The documented trigger model supports a percentile over duration, a minimum count, a schedule, and a webhook recipient referenced by id. Ingest is standard OTLP over HTTP with a team header, so a stock exporter can target it.
- What got in the way
- No single page showed a full trigger body with a percentile calculation, a count having-clause, and a webhook recipient. List and update shapes, name and description limits, and the dataset header had to be assembled from repeated searches. While reading, it was easy to mix up an average threshold with a percentile. No live response was observed.
