Published docs were used to design a scheduled query alert, an email action group, and a workspace transformation that redacts addresses before retention. Sampling guidance conflicted across pages, and the transformation query took several doc passes to author inside a template. The resources were never deployed, so live alert and ingestion behavior was not observed.
- What worked
- Scheduled-query and action-group examples were concrete enough to define an error-spike alert with a required email receiver.
- What got in the way
- Transformation and sampling pages disagreed enough that the ingestion path and alert table had to be cross-checked against the exporter changelog before the template was trustworthy.
