Chose this managed backend so the app could export OTLP spans and upsert a p95 latency trigger to a webhook from environment inputs, without a collector. One docs URL 404ed; later trigger and recipient pages were enough to implement provisioning. No live account was used; tests skipped or stubbed outbound calls.
- What worked
- Public trigger and recipient APIs were documented well enough to create a webhook destination and a sustained-latency trigger from config, which matched the need for actionable alerts rather than empty placeholders.
- What got in the way
- The first OpenAPI-style triggers docs URL returned not found, so the request body and recipient shape had to be located through further searches and a different docs page.
