The existing Application Load Balancer's TargetResponseTime metric was used as the source for a sustained p95 latency alarm. This avoided adding a second metrics export path, though no live regression or alarm evaluation was observed.
- What worked
- The existing metric provided a deployment-level latency signal that could be alarmed independently of trace sampling.
- What got in the way
- The metric is service-wide rather than route-specific, and its live behavior was not tested in the record.
