Summary of the problem : As a user I want to quickly identify if there is an error and know what the underlying root cause of the problem is.

User stories:

List known (technical) restrictions and requirements

• Add a new error rate chart [APM] Add error rate chart to Errors overview and detail views kibana#65619 | [APM] Add error rate chart to Errors overview and detail views kibana#67327
  • Number of transactions / number of error occurrences = error rate
• Annotate the error rate chart with versions. [APM] Add error rate chart to Errors overview and detail views kibana#67327
• Reorganize the Errors overview list information [APM] Errors overview list redesign kibana#68261
  • Add "new" error indicator
  • Remove the Group ID column?
  • Add Transaction name column?
• Surface new errors to the top of table and tag them so they stand out. [APM] Errors overview list redesign kibana#68261
  • New errors are defined by looking at when the error group's first occurrence was seen and showing "new" on error groups that have had their first occurrence within the last 7 days.

Descoped for initial design proposal

• Surface root cause of the issue by comparing the error with the other Transactions of the same type.
  • This is tied in with ML integration on a new unique errors job
• Annotate the error chart to show triggered alerts.
  • We will be annotating alerts on all time-series charts in APM, so this will be resolved when that happens (see [APM] Display threshold alert annotations on time-series graphs kibana#60373)
• Add compare to a week ago to the error rate chart.

Meta issue: #223