# Add refresh and (or) live option to query log

**URL:** <https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262>\
**Category:** Implemented\
**Created:** [May 30, 2019, 4:26pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262 "2019-05-30T16:26:24Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![poiromaniax](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/poiromaniax/32/8305_2.png) [@poiromaniax](https://discourse.pi-hole.net/u/poiromaniax)\
**Post date:** [May 30, 2019, 4:26pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/1 "2019-05-30T16:26:25Z")

</div>

Hey all,

Love love love Pi-Hole!

But a feature that seems to be missing for me is a simple refresh button on the query log page. Would also be great to have a checkbox or option that allows one to view the requests in real time.

As it is, I have to constantly refresh the page for new entries

---

<div class="post-metadata">

**Author:** ![RamSet](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/ramset/32/3497_2.png) [@RamSet](https://discourse.pi-hole.net/u/RamSet)\
**Post date:** [May 30, 2019, 4:31pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/2 "2019-05-30T16:31:30Z")

</div>

That option is available under Tools /Tail pihole.log

You get to actually see what's queried, what's replied and who requested it 🙂

 ![image](https://discourse.pi-hole.net/uploads/default/original/2X/0/0327e5f5cfe80297da0883832de53d7b72cf8fe5.png)

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [May 31, 2019, 2:37am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/3 "2019-05-31T02:37:11Z")

</div>

An even prettier option is to run the command `pihole -t` from the command line. That will color code the output, showing the blocked entries and queries in different colors.

---

<div class="post-metadata">

**Author:** ![symbiot78](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/symbiot78/32/7455_2.png) [@symbiot78](https://discourse.pi-hole.net/u/symbiot78)\
**Post date:** [May 31, 2019, 7:22am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/4 "2019-05-31T07:22:49Z")

</div>

On the query page a "live" option would be great. Also, and more importantly allow me to refresh the log WITH whever device I selected.  
Refreshing the log always clears the selection and I have to reselect.

Allowing to select multiple devices and having live refresh would also be fantastic.

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [May 31, 2019, 7:26am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/5 "2019-05-31T07:26:58Z")

</div>

> [@symbiot78](#):
>
> Also, and more importantly allow me to refresh the log WITH whever device I selected.  
> Refreshing the log always clears the selection and I have to reselect.

When you start the Query Log from a link on the dash board (e.g. in the Top Clients list), you can refresh as often as you like and only the requested client will be shown. Even more only the data for this particular client is sourced from the Pi-hole so the page should also load somewhat quicker.

---

<div class="post-metadata">

**Author:** ![poiromaniax](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/poiromaniax/32/8305_2.png) [@poiromaniax](https://discourse.pi-hole.net/u/poiromaniax)\
**Post date:** [June 2, 2019, 11:13am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/6 "2019-06-02T11:13:35Z")

</div>

yes there is the tail log and CLI but it would be nice to watch the request come into the actual query log and be able to action the buttons to whitelist or blacklist

---

<div class="post-metadata">

**Author:** ![ilovecats516](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/i/dbc845/32.png) [@ilovecats516](https://discourse.pi-hole.net/u/ilovecats516)\
**Post date:** [July 26, 2019, 3:27am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/7 "2019-07-26T03:27:19Z")

</div>

I agree. Having the option to blacklist queries as they come in would be nice.

---

<div class="post-metadata">

**Author:** ![PHKomrad](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/phkomrad/32/2222_2.png) [@PHKomrad](https://discourse.pi-hole.net/u/PHKomrad)\
**Post date:** [January 14, 2018, 7:24pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/8 "2018-01-14T19:24:24Z")

</div>

When actively troubleshooting a domain blocking issue, I refresh the Query Log page periodically to see if my change fixed the issue. I currently use my browsers page reload button or click on the navigation log to refresh the page.

# Problems with the current setup

**User Experience** It seems like there should be a refresh button that does this since there's a use case for it within the app. The 1st thing a user will look for is a refresh button when they want to refresh the results . when they don't find one, they will interrupt their work to go hunt for a way to refresh the page.  
**Consistency** Other pages like the whitelist and blacklist pages, have this, why doesn't this page have it?

# Icing on the cake

**Automatic refresh** aka tailing the log . This is something that I do daily at my job when monitoring a process. This would make troubleshooting easier as changes and monitoring are done from the same Web app. Users can ssh to their pi-hole server and tail logs if they'd like, but this would give them another , convenient option.

---

<div class="post-metadata">

**Author:** ![Mcat12](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mcat12/32/20_2.png) [@Mcat12](https://discourse.pi-hole.net/u/Mcat12)\
**Post date:** [January 14, 2018, 9:17pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/9 "2018-01-14T21:17:44Z")

</div>

You can use the tail log feature or `pihole -t` (the command line version). A refresh button would functionally be the same as just reloading the page since there is little performance difference (unless we implemented partial reloading or event streams).

---

<div class="post-metadata">

**Author:** ![PHKomrad](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/phkomrad/32/2222_2.png) [@PHKomrad](https://discourse.pi-hole.net/u/PHKomrad)\
**Post date:** [January 15, 2018, 12:50am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/10 "2018-01-15T00:50:44Z")

</div>

I know. But if you want to pi-hole web app to behave like an application(UX), then the buttons and menu's will be in the application. Going outside of the app to use browser or even worse ssh'ing to run commands in a shell detracts from that.

It's also more convenient to do it right from the Web page. Once I'm done with my current project I might go back and tack a refresh button and/or log monitor web tool onto pi-hole and submit a merge request.

---

<div class="post-metadata">

**Author:** ![yubiuser](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yubiuser/32/12100_2.png) [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)\
**Post date:** [November 30, 2023, 10:42pm UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/11 "2023-11-30T22:42:23Z")

</div>

> <https://github.com/pi-hole/web/pull/2880#pullrequestreview-1758495726>
>
> \# What does this implement/fix?
> 
> This PR adds a checkbox for enabling/disablin…g live Query Log updates.
> 
> !\[Screenshot from 2023-11-28 23-52-50\](https://github.com/pi-hole/web/assets/16748619/c770ce4c-25e0-4274-a8a3-a3fff3b4673e)
> 
> 
> This enhancement improves the user experience by providing more flexibility in how the recent queries are displayed and updated.
> 
> \*\*Related issue or feature (if applicable):\*\* N/A
> 
> \*\*Pull request in \[docs\](https://github.com/pi-hole/docs) with documentation (if applicable):\*\* N/A
> 
> \---
> \*\*By submitting this pull request, I confirm the following:\*\* 
> 
> 1. I have read and understood the \[contributors guide\](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 
> 2. I have commented my proposed changes within the code.
> 3. I am willing to help maintain this change if there are issues with it later.
> 4. It is compatible with the \[EUPL 1.2 license\](https://opensource.org/licenses/EUPL-1.1)
> 5. I have squashed any insignificant commits. (\[\`git rebase\`\](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
> 
> \## Checklist:
> 
> \- \[x\] The code change is tested and works locally.
> \- \[x\] I based my code and PRs against the repositories \`developmental\` branch.
> \- \[x\] I \[signed off\](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the \[DCO\](https://docs.pi-hole.net/guides/github/dco/) for all contributions
> \- \[x\] I \[signed\](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
> \- \[x\] I have read the above and my PR is ready for review.

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [July 12, 2026, 11:16am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/12 "2026-07-12T11:16:53Z")

</div>

Pi-hole v6's Query Log has a live view that streams new queries in real time, so no manual refresh is needed. Marking this as implemented.

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [July 12, 2026, 11:16am UTC](https://discourse.pi-hole.net/t/add-refresh-and-or-live-option-to-query-log/20262/13 "2026-07-12T11:16:57Z")

</div>

Closed on July 12, 2026, 11:16am UTC


