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

[Feature] Document count for average/sum aggregation on Tile map #10297

Closed
anhlqn opened this issue Feb 10, 2017 · 1 comment
Closed

[Feature] Document count for average/sum aggregation on Tile map #10297

anhlqn opened this issue Feb 10, 2017 · 1 comment

Comments

@anhlqn
Copy link
Contributor

anhlqn commented Feb 10, 2017

Describe the feature:
This feature applies to some situations:

  • Average response time of web page
  • Sum of client request or server response bytes
  • Unique of client IP
  • also other use cases

When graphing average response time or other aggregation except for Count, it is very helpful to know how many documents/events that countribute to the aggregated value. For instance, if avg response time for certain client IPs is above 10s, but the number of requests each IP is lower than 50, perhaps they are just some scanners or bots that crawling our website.

I know that we can create a tile map using Count and put side by side to compare, but again I would love to just see the information on one tile map when hoovering over a data point on the map.

To display both figures, main aggregation and the document count, we can either:

  • Put both on each data point
  • Use Color for main aggregation and dot size for document count or vice versa

Is it something that requires lots of work to implement?

@anhlqn anhlqn changed the title Document count for average/sum aggregation on Tile map [Feature] Document count for average/sum aggregation on Tile map Feb 10, 2017
@tbragin
Copy link
Contributor

tbragin commented Feb 13, 2017

I think this is a more specific instance of what is being requested in #6279

I will add your comment there, and close this issue.

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

No branches or pull requests

2 participants