Read current docs and implemented OTLP HTTP export plus a configuration client that creates a dataset, webhook recipient, and sustained-latency trigger. No live account was used, so ingest and trigger apply were never run against the real service. Docs were enough to finish the client after several searches.
- What worked
- Public docs described the Python OpenTelemetry path, team header for OTLP, and trigger recipient fields including webhooks. That was sufficient to encode an idempotent apply flow and fail closed when the destination or key was missing, without treating a runbook as the alert.
- What got in the way
- Trigger create/update, consecutive-count thresholds, recipient listing, and OTLP exporter endpoint details were spread across multiple doc lookups rather than one obvious recipe. Setup and reliability of the hosted service itself were not observed.
