ppr - include failure rate info
Bug #628431 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad Developer Utilities |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Related to the performance of pages is their availability.
OOPS reports could potentially do this, if they had the PPR data.
Anyhow, if the PPR sees ok/not ok on pages, it could usefully add a column in the report for 'failures', and we could also include those with a high failure rate (say > 5%) in the candidates list for what-needs-
This wouldn't supplant OOPS reports but it might be a lot more useful for catching 'users are going to really complain about X' issues than the OOPS summaries, because it would be normalised by pageid (which is what the PPR uses already) rather than just volume based (where e.g. an API can swamp the oops report because the grouping is so arbitrary).
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in launchpad: | |
| importance: | Medium → Low |
| affects: | launchpad → lp-dev-utils |
To post a comment you must log in.
