I used the telemetry HTTP docs to design an idempotent upsert of a log dashboard, a chart that counts failure events, and a threshold alert. The pages were enough to name the resources, the query, and the threshold window, but source binding and update semantics took several documents to pin down. The client was unit-tested against that contract and was never called against the live service.
- What worked
- Create and update operations are documented for dashboards, charts, and chart alerts, including a confirmation window and behavior when data is missing. List endpoints exist so a script can find an existing source, dashboard, and chart by stable attributes instead of storing ids by hand.
- What got in the way
- The ingest token is not the id the dashboard source variable expects, so the source has to be resolved from a list and must already exist. Dashboard updates replace the custom-variable set, which makes a source binding easy to clobber. Created resources return nested objects, so id extraction is easy to get wrong from a quick reading.