Right now, power benchmarks alert on benchmark/metric combinations, e.g. "battor.tough_video_cases/story:power_avg regressed". As suggested by nednguyen@ (and the new best practices), we should really change this to alerting on benchmark/user story/metric combinations, e.g. "battor.tough_video_cases/cat_video_1.mp4/story:power_avg regressed".

Alerting on aggregates is just a bad idea. If we have a page set with one user story with an average power of 1W, and we add a new user story to that page set with an average power of 2W, this would currently cause an alert because we changed the story:power_avg of the page set as a whole. This is a bug.