-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Collapsed query log for time series data #1164
Labels
Comments
This looks really nice, it would definitely help analysing traffic from each client as it shows exactly how many unique domains are visited and how they relate to overall request count. |
This was referenced Nov 24, 2019
ghost
mentioned this issue
Jan 28, 2020
ghost
mentioned this issue
Feb 28, 2020
This was referenced May 22, 2020
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(bit hard to imagine whether AG interest to implement this feature due quite annoying task however prefer keep in issue list)
Problem Description
Sometimes i hear this question from network monitoring tools users then solution usually backup and sort logs(databases) using third-party software that designed to data analysis but some proprietary monitoring tools come with this facility as well
If we consider our one personal mobile device as example may have 6000 queries for a week and too difficult to read one by one to identify each but might be only 300-400 domains, we can view easily within 4 pages in collapsed query log. just i dont need to explain about benefits
(note: it's not possible to accomplish this requirement using client based top queried domains #481 (comment))
Proposed Solution
To make this easy, it's convenient to set a option (check box:: collapse query log) only usable per one client with specific date and time range. (ex: max - one month)
(this feature will fulfill the rest #594 (comment))
(query log default mode)
(collapsed query log)
[1] check box. [2] expand button(optional)
(optional: expand each domain queries)
#697
The text was updated successfully, but these errors were encountered: