-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Comparison panel #645
Labels
Comments
It would be great feature. |
I agree, great idea |
+1 |
Agree |
+1 |
May be usefull here too, the ability to compare in histograms but also in the hits view, typically in table mode we may add a variation column in %. |
+1 |
1 similar comment
+1 |
+1 would use this feature everyday |
+1 |
1 similar comment
+1 |
+10 ! |
it will be great +1 |
Was this turned into an enhancement? Otherwise +1 |
👍 @bobrik why was this closed? |
+1 |
Any info on this? +1 |
When will we have this? |
w33ble
pushed a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
This was referenced Jul 10, 2020
This was referenced Aug 17, 2020
This was referenced Aug 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's pretty important for us to compare periods of time in stats.
Here's liveinternet.ru pageviews stats that compares current day with previous day:
It growth is slowing down — you can see it right away, compare this with regular view where you see two days one after another.
We have our own statistics viewer that has similar functionality: you can compare values hour by hour in today vs yesterday view.
It's easier to spot time when something happened.
I think it could be done in separate panel in kibana too, where you can pick comparison interval (actual width of the panel on time axis) and time interval just like in histogram panel. Histogram will have (number of queries)*(number of intervals) groups of bars.
I wonder if this is in roadmap. If it's not, we'd like to implement it and merge into kibana. It would be great to see some feedback too.
The text was updated successfully, but these errors were encountered: