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

[APM] Performance comparison charts by user agent (browser) #43342

Closed
sorenlouv opened this issue Aug 15, 2019 · 1 comment · Fixed by #49582
Closed

[APM] Performance comparison charts by user agent (browser) #43342

sorenlouv opened this issue Aug 15, 2019 · 1 comment · Fixed by #49582
Assignees
Labels
roadmap Team:APM All issues that need APM UI Team support v7.6.0

Comments

@sorenlouv
Copy link
Member

sorenlouv commented Aug 15, 2019

Summary

APM RUM users can enable collecting user agent information. This helps customers using RUM monitoring to view performance comparison charts by user agent.

Avg. page load duration distribution by browser

Chart - Avg  page load duration distribution by browser

  • Much like the region map, we'll also render a time-series chart grouped by the user-agent.browser for the selected time range. The KPI element in the chart will show the top browser.
  • Hovering on the chart will show the duration avg's for each time bucket for each browser agent

Full page screen examples

Just to show examples of the full layout.

01 - RUM - Page loads - Top level

02 - RUM - Page load detail

@sorenlouv sorenlouv added Team:APM All issues that need APM UI Team support [zube]: Impl Backlog labels Aug 15, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@sorenlouv sorenlouv changed the title [APM] Performance comparison charts by user agent [APM] Performance comparison charts by user agent (browser) Aug 28, 2019
@smith smith self-assigned this Oct 28, 2019
smith added a commit to smith/kibana that referenced this issue Nov 20, 2019
Show a chart with average page load broken down by user agent name on the RUM overview.

I tested this by setting up a RUM agent on a sample app on my test cloud cluster.

On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests.

Fixes elastic#43342
smith added a commit that referenced this issue Nov 20, 2019
Show a chart with average page load broken down by user agent name on the RUM overview.

I tested this by setting up a RUM agent on a sample app on my test cloud cluster.

On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests.

Also factor out the color selection into a common helper.

Fixes #43342
@zube zube bot reopened this Nov 20, 2019
smith added a commit to smith/kibana that referenced this issue Nov 20, 2019
…49582)

Show a chart with average page load broken down by user agent name on the RUM overview.

I tested this by setting up a RUM agent on a sample app on my test cloud cluster.

On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests.

Also factor out the color selection into a common helper.

Fixes elastic#43342
smith added a commit that referenced this issue Nov 20, 2019
Show a chart with average page load broken down by user agent name on the RUM overview.

I tested this by setting up a RUM agent on a sample app on my test cloud cluster.

On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests.

Also factor out the color selection into a common helper.

Fixes #43342
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Team:APM All issues that need APM UI Team support v7.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants