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

Mitigate outliers in transaction duration histogram visualization #305

Open
graphaelli opened this issue Jul 30, 2020 · 4 comments
Open
Assignees
Labels

Comments

@graphaelli
Copy link
Member

Is your feature request related to a problem? Please describe.

Wide ranges of values in distribution of transaction duration make visualization and drilling down difficult.

The evenly spaced buckets are great when the durations are clustered:

image

Add single outlying (not necessarily statistical outliers) value and the picture is muddier

image

The drill down can be worked around using the kuery bar, eg transaction.duration.us> 40000 and transaction.duration.us< 100000, but visualizing the overall distribution remains a challenge.

Describe the solution you'd like
Both situations could be better with a non-linear x-axis. I'd like to prototype a view where very large ranges are visually split into groups, perhaps 0-100ms, 100ms-500ms, 500ms-1s, 1s+ for a start. Since this histogram is used both for web traffic, which is typically fast and log normally distributed as well as background tasks, something fancier that adjusts based on the distribution might be in order.

@felixbarny
Copy link
Member

++ for this, just some additional thoughts
Could navigating from the transaction duration chart to exemplar transactions help for this use case? #300 (comment)

Being able to select a range of buckets similar to how it's possible to select a time range by selecting an area in a chart could also help.

@graphaelli
Copy link
Member Author

I agree there is overlap, commented on the related issue.

@mikker
Copy link
Contributor

mikker commented Aug 4, 2020

I like both your suggestions. I think Felix' idea of zooming in on a range sounds like the natural interaction, and users already know it from the response time/rpm graphs.

@elasticmachine
Copy link
Contributor

Pinging @elastic/observability-design (design)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants