+1. I have a friend whose Roku devices make his Query Log largely unusable due to how noisy they are, an order of magnitude above the surrounding numbers. It would be useful to be able to not show selected domains in the Query Log. But I'm also mindful of @DL6ER's comment about how using filters, especially wildcards, across the databases will scale badly and impact performance, and his other comment about avoiding yet more filter lists.
Would it be possible to implement this just for rendering the static Query Log, and just up to 100 items?
- Long-term query database logging – no change in behaviour
- /var/log/pihole.log logging – no change in behaviour
- API exporting – no change in behaviour
- Query Log with show all (
queries.php?all) – no change in behaviour - The entries in Settings > API / Web interface > Top Domains & Top Clients – continue to function as they do today, with a new additional interpretation below
- Query Log with 10, 25, 50, 100, All selected – exclude unwanted domains when the page is manually loaded
- Unwanted domains are the same ones listed in the aforementioned two sections
This would satisfy my friend's needs, since his disproportionately noisy devices would no longer dominate his Query Log when inspecting the current activity, and they already would be excluded from the Top lists in the Dashboard.
I suspect this is how most people would make use of being able to block noisy domains. It's not for system-wide filtering, just to silence awkward domains when viewing current activity. I am guessing that for most casual home users with the likes of Roku and Samsung devices, being able to see the 100-entry Query Log is good enough if they can do so without these devices showing.
Would this implementation allow domains to be exluded from the Query Log without the scaling, performance and management impacts?