OOPS when a branch takes too long to scan

Bug #109591 reported by Jonathan Lange
This bug report is a duplicate of:  Bug #44205: supermirror latency monitoring. Edit Remove
2
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

<spiv> It would be nice if we got an OOPS every time a branch hits 10 minutes after being pushed without being scanned.

Tags: lp-code
Revision history for this message
Jonathan Lange (jml) wrote :

<lifeless> a report might be better than an oops
 this is a sla metric rather than an operational error.
<spiv> Quite likely.
<lifeless> e.g. get it in cricket or something like that.
<spiv> Just having cold hard figures (and enough details that we can investigate individual cases if necessary) is the main thing.
 I don't mind too much what the format is, although it would be good to be notified when it takes too long (and to be good enough that we rarely get the notification).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.