Alexei - is the best way of monitoring the max & 0 buckets to look at the 1st (0th?) and 99.9999th percentiles?

Or is there a better way?

We should also monitor mean since various teams (AGSA, search, mdw) depend on it.

+1 to proposal to monitoring 1st percentile and something in the extreme tail (99.9 or 99.99) as well.

note that we need to monitor mean in addition to the tail since it's still possible there's a significant change further in the tail which wouldn't be caught at 99.99 but still regresses the mean.

Ushesh, I think this is a good example of why our process for FCP should be different from other heartbeat metrics.

We shouldn't bother monitoring mean for other heartbeats, but need to for FCP.

Alexei - any thoughts on #1?

Sorry, somehow missed this. We don't have a better way at the moment.

This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.

Issue has a component, but no priority. Updating to have default priority (Pri-2)

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

I've set up these alerts.