mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Query log: Add option to Show drop-down for showing domains that haven't triggered a rule #1722
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#1722
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @twcau on GitHub (Jun 29, 2020).
Problem Description
At present, Query log has a small number of filters and options to reduce the data shown. Most issues for improving it are the subject of other feature request tickets.
But something that isn't is the options available in the drop-down to choose what is shown.
At present, the options are either:
However, there's no way to see only what hasn't been filtered. This means the user can't focus and simplify on finding those domains that may need attention; as the results included all the filtered (or permitted by rule) content.
Proposed Solution
For the Show... drop down, add a new option called Show Passed, which shows only those records with a filtering status of Ellapsed (according to the querylog.json file with all the logging).
This would then allow the user to only see those domains that haven't triggered a rule, and proceed accordingly.
Alternatives Considered
No plausible alternatives identified.
Additional Information
N/A
@Aikatsui commented on GitHub (Jun 30, 2020):
Duplicate of #882
@ameshkov commented on GitHub (Jul 2, 2020):
Already resolved in the beta version: