Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RUM Dashboard] add impactful metrics panel(JS Errors) #73037

Closed
katrin-freihofner opened this issue Jul 23, 2020 · 1 comment · Fixed by #77919
Closed

[RUM Dashboard] add impactful metrics panel(JS Errors) #73037

katrin-freihofner opened this issue Jul 23, 2020 · 1 comment · Fixed by #77919
Assignees
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan test-plan-ok issue has passed test plan v7.10.0

Comments

@katrin-freihofner
Copy link
Contributor

katrin-freihofner commented Jul 23, 2020

Describe the feature:

We would like to extend the RUM dashboard with a new panel. The panel holds two sections:

  • a list of JavaScript errors

Frame 16

JavaScript errors

This section holds:

Headline JavaScript errors + icon iInCircle

2 Stats (small):

  • total number of errors in the selected timeframe
  • the error rate

Screenshot 2020-07-23 at 13 58 43

A table with the top 5 JavaScript errors

sorted by impacted page loads; pagination

Columns:

  • error message
  • impacted page loads

Design issue

@shahzad31 shahzad31 changed the title [RUM Dashboard] add impactful metrics panel [RUM Dashboard] add impactful metrics panel(JS Errors) Sep 18, 2020
@shahzad31 shahzad31 added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label Sep 18, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan test-plan-ok issue has passed test plan v7.10.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants