Add block list name column in Query Log

Feature Requests
1

From GitHub:

I realize this will be prioritized below bug fixes etc. but it would be really nice to be able to tell which block list is blocking a query in the query log in the web interface. This is especially true for someone who's added a lot of other block lists in addition to the default pi-hole block lists. I believe it would be best to first add the ability to give custom "common" names to each block list URL in pi-hole settings under "Pi-Hole's Block Lists", those "common" names of each block list you can manually define would then be pulled into the Query Log as a new column for easy reference of which block list is creating issues or blocking things that, for instance, you would not suspect it should be blocking.

Perhaps by default the filename at the end of the block list URL such as "examplelist.txt" would be what the common name is set to minus the file extension (e.g. "examplelist") however you could then change it manually to what you desire to call it which would then appear in the Query Log as a new column.

[Update] After thinking about this a bit further I believe this would require more effort or might not be "doable" without some changes unlike I had originally thought. Since all the ad/block lists are aggregated and de-duped we would have to probably create some type of lookup table/database prior to list aggregation and de-duplication for the Query Log in the web GUI to reference. Additionally since there could be lists that have the same domains in them the feature would have to support multiple columns in the query log for all the lists that had the domain within them prior to aggregation and de-duplication....just more thoughts, curious to hear back on feasibility.

Thank you!

2

Hi everyone!
I think there is a good idea:
Shows which blocklist the domain name is blocked from.

So at present, we cannot see the blocked domain is blocked from which blocklist, we can only see that the domain is blocked by blocklists.
By add this function, we can see which blocklist the domain name is blocked from.

1 Like
3

Pi-hole is using only one blocklist for filtering: Gravity.

For speed as well as memory load, Gravity is created by combining all your configured blocklists into a single consolidated blocklist that will contain a domain name only once, even if it appears in mutiple blocklists or multiple times in any one blocklist.
So the source for any domain blocked by a list would always be Gravity.

Also, logging all blocklists a domain name appears on, even if it would be possible, would quickly clog your logs with information you will most likely never look at.

In circumstances where you have to find out which lists do block a certain domain or whether that domain would be blocked at all, that information is easily available via Pi-hole's Tools | Query Lists.

1 Like
4

When I'm viewing a query log, there is a controllable limit of total queries to be displayed, of which blocked queries make up a varying fraction of. As I wondered in my matching feature request, would it still be a performance risk if those block lists were only evaluated when the queries were displayed (and just for the queries displayed)? If it were noticeable, perhaps a checkbox to let the viewer decide whether or not to display the blocklist (off by default).
Just thinking aloud here. Thanks!