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

Show currently selected bucket in transaction group page histogram #24740

Closed
1 task
jasonrhodes opened this issue Oct 29, 2018 · 2 comments · Fixed by #26266
Closed
1 task

Show currently selected bucket in transaction group page histogram #24740

jasonrhodes opened this issue Oct 29, 2018 · 2 comments · Fixed by #26266
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support v6.6.0

Comments

@jasonrhodes
Copy link
Member

screenshot 2018-10-24 at 10 45 26

When entering the transaction detail page from the Traces overview, the histogram doesn't always show the selected bucket that the sample displayed is from. (This happens when the transaction you are visiting is not the same as the sampled transaction for that duration group in the histogram data.)

AC:

  • Selected bucket is visually styled when arriving at a transaction group page with a selected transaction ID, the same as it usually is when regularly arriving at a transaction group page

See comments here for proposed solutions:

@jasonrhodes jasonrhodes added Team:APM All issues that need APM UI Team support [zube]: Inbox labels Oct 29, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@alvarolobato
Copy link

The discussed solution is in this line: When we are loading the histogram we will pass the trace/transaction currently loading and make sure it is loaded from elasticsearch in the right bucket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support v6.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants