Open Bug 1729665 Opened 3 years ago Updated 2 years ago

Add a performance tab in Push Health

Categories

(Tree Management :: Perfherder, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: sclements, Unassigned)

References

(Blocks 1 open bug)

Details

The idea is to build upon and improve the existing performance tab in Treeherder but change the data that is shown and improve the UX. This new feature will be added to the the existing tabs panel in Push Health.

Dave and Alexandru, please help list the requirements (and any helpful technical details) you see that need to be done to improve this tab. Some I recall from the meeting were:

  • Only show tests we care about and that we alert for (how would one find what those are?)
Flags: needinfo?(dave.hunt)
Flags: needinfo?(airimovici)

(In reply to Sarah Clements [:sclements] from comment #0)

The idea is to build upon and improve the existing performance tab in Treeherder but change the data that is shown and improve the UX. This new feature will be added to the the existing tabs panel in Push Health.

Dave and Alexandru, please help list the requirements (and any helpful technical details) you see that need to be done to improve this tab. Some I recall from the meeting were:

  • Only show tests we care about and that we alert for (how would one find what those are?)

Here are my thoughts:

  • Only show tests that we alert on (hide any where shouldAlert is false)
  • Provide links to the test documentation (we have been doing this in bug 1698545 and dependencies)
  • Provide some form of comparison to allow the viewer to identify if there may be a need to investigate

For the final point, the best comparison would be the same test without the changes from the push applied but in most cases we won't have this. We could instead provide the avergage and standard deviation for the test over the last 7 days on mozilla-central, or maybe even show a compact data visualisation.

Flags: needinfo?(dave.hunt)
Flags: needinfo?(airimovici)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.