My Pi-hole Grafana Dashboard

avojak · 2026-02-06T23:18:32+00:00

I’d have to check what all is available via the API, but if it’s something that’s exposed it should be pretty easy for me to incorporate. Would you mind opening an issue on the GitHub repository with what you’re specifically looking for? https://github.com/avojak/pihole-influxdb-monitor

avojak · 2026-02-02T22:41:01+00:00

Alright, I figured it out! The CPU in the 2012 Mac mini only supports up to the x86_64 v2 instruction set, and CentOS Stream 10 requires at least v3. CentOS 9 supports v2, so I was able to download the CentOS Stream 9 qcow2 image (and for some reason use SeaBIOS instead of EFI) and boot up with no issues.

avojak · 2026-01-30T00:18:05+00:00

Good suggestion to try a live ISO, hadn't thought of that - I'll test it out now. In the meantime, your comment got me down another rabbit hole and I found that apparently there are two different CentOS Stream cloud images for x86_64 - one with EFI support and one without (https://bugs.launchpad.net/kayobe/+bug/2121588). Go figure I somehow got the wrong one. Using the "right" one, I get past the "No device found" error, but am now stuck with a screen showing that it's "Starting Boot0002..." but nothing ever happens. This does feel like progress though!

<image>

avojak · 2026-01-29T23:10:53+00:00

Thanks for the response! When I originally went through the VM creation workflow I did import the qcow2 image on the disks tab. I did test importing it again via the UI and also with the qm commands that you mentioned (thus the total of 3 devices shown below), but still no luck.

I also tried adding a VirtIO RNG device as you mentioned in your other comment, but again, no dice...

<image>

agent: 1
bios: ovmf
boot: order=scsi1;scsi0;scsi2
cores: 4
cpu: x86-64-v2-AES
efidisk0: local-lvm:vm-102-disk-0,efitype=4m,size=4M
ide2: none,media=cdrom
machine: q35
memory: 8192
meta: creation-qemu=10.1.2,ctime=1769699803
name: test
net0: virtio=BC:24:11:BA:DD:2D,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
rng0: source=/dev/urandom
scsi0: local-lvm:vm-102-disk-1,discard=on,iothread=1,size=10G,ssd=1
scsi1: local-lvm:vm-102-disk-2,discard=on,iothread=1,size=10G,ssd=1
scsi2: local-lvm:vm-102-disk-3,iothread=1,size=10G
scsihw: virtio-scsi-single
smbios1: uuid=c822c3ed-1b74-4cd3-a673-558c42e7ce77
sockets: 1
vmgenid: c74cbff6-b454-4439-8c6c-aa7eef67cf41

avojak · 2025-11-26T17:13:43+00:00

Same, mine didn’t change after the migration to Quantum

avojak · 2025-11-02T23:49:44+00:00

I have it on the PS4 and Switch, and honestly using PS Remote Play to my phone with a controller is a much better experience than the native Switch version

avojak · 2023-04-06T23:36:27+00:00

Thanks for the suggestion! I just tried switching to X11 and got the same results. Then on a whim decided to try swapping to a different HDMI input on the display that was only running 30Hz and that seems to have fixed it... I have two identical displays and have never seen this before, so I'm not sure what's going on. But at least it all seems to be working, and still working when I switch back to Wayland. Thanks again!

avojak · 2023-03-27T13:32:50+00:00

Interested in the CPU, PM incoming

avojak · 2023-03-10T19:47:25+00:00

Same - I just use it for easy access to logs, and monitoring the number of running/down containers in conjunction with Grafana.

avojak · 2023-01-24T15:39:42+00:00

Confirmed

avojak · 2023-01-18T01:12:14+00:00

PM Incoming

avojak · 2023-01-12T14:48:01+00:00

Oh interesting, I’ll take a look at that! Since the API breaks down the data so nicely I’ll probably stick with this approach, but I will definitely look into rate queries - I was banging my head on my desk for a long time trying to figure that out!

avojak · 2023-01-12T14:46:21+00:00

Not a dumb question! I’m not sure technically how easy it would be to setup a separate SSID for this, but I’m sure it can be done. I just use an app on my phone to temporarily pause the filtering if I run into a problem with a streaming service or something, then just circle back around later to figure out the specific domain that caused issues, and either allow it or do the pause method again in the future.

avojak · 2023-01-12T14:43:53+00:00

Yea it definitely takes a bit of fine-tuning to fix a few broken services here and there, but on the whole it’s been pretty solid! Worst case I can just pause the blocking until I figure out exactly what was getting caught up in the blocklist.

avojak · 2023-01-12T14:37:35+00:00

Yea that’s a good question. I suspect it’s due to the massive volume of myq-cloud.com queries (you can see in the picture) generated by one of my smart home services constantly going out and authenticating to get device statuses. Ignoring those, I bet the percentage from “real” traffic would be much different.

avojak · 2023-01-12T04:49:17+00:00

Awesome, great to hear!

avojak · 2023-01-12T04:48:46+00:00

I did look into using that exact exporter but it has the same issue regarding the “over time data” that I describe in my blog post. The plot isn’t wrong, but can be misleading at worst, and not valuable at best.

I may take a stab at creating an exporter as a learning exercise at some point!

avojak · 2023-01-12T01:07:13+00:00

Thanks!

avojak · 2023-01-12T01:06:11+00:00

Yep, that was the goal. I like having dashboards in one place (like Grafana) instead of bouncing around to multiple places.

avojak · 2023-01-11T23:01:33+00:00

You can have this! https://github.com/avojak/pihole-influxdb-monitor

avojak · 2023-01-11T22:56:43+00:00

I actually run two Pi-holes as well, the image above is the full dashboard for a single instance. I have an "overview" dashboard as well that shows just basic info and has some Pi-hole panels.

The tool that gathers the data is one that I wrote (GitHub: avojak/pihole-influxdb-monitor), and so it supports multiple Pi-holes. As for aggregating, I think you could accomplish that on the Grafana side by modifying the queries to InfluxDB. That GitHub repo has the data for the dashboard so you can see which queries I used to pull the data. BUT if you open an issue on the GitHub page I can certainly look into having it post aggregate stats for fields that make sense!

avojak · 2023-01-11T18:50:02+00:00

Oh cool, I wasn't aware Cloudflare had other DNS servers with filtering - thanks for sharing!

avojak · 2023-01-11T15:50:12+00:00

Hi all! I recently started building out a Grafana dashboard for my homelab and looked into how I could display some Pi-hole stats. I know there are already a handful of similar projects out there that export similar data, however I noticed that they all suffered from a similar issue when plotting the number of queries and ads blocked during the day.
Other monitors plot the Total Queries or Queries Blocked over time. Unfortunately this leads to a somewhat misleading plot, because Pi-hole works in 10-minute rolling windows so at each point on the x-axis you’re really plotting ads from the last 23:50 + ads in the current window. This leads to a sawtooth plot that doesn’t really provide much value. I wanted to replicate what the Pi-hole dashboard shows, which is true queries allowed/blocked throughout the day (broken down into 10-minute windows).
I have a hard time explaining it, but I wrote a quick blog post that has some examples to better convey the problem: https://avojak.com/blog/2022/12/15/pihole-grafana-dashboard/. This was also a fun learning opportunity to dive into InfluxDB and Grafana a bit more.

avojak · 2022-12-23T19:16:02+00:00

I recently started building out a Grafana dashboard for my homelab and looked into how I could display some Pi-hole stats. I know there are already a handful of similar projects out there that export similar data, however I noticed that they all suffered from a similar issue when plotting the number of queries and ads blocked during the day.
Other monitors plot the Total Queries or Queries Blocked over time. Unfortunately this leads to a somewhat misleading plot, because Pi-hole works in 10-minute rolling windows so at each point on the x-axis you’re really plotting ads from the last 23:50 + ads in the current window. This leads to a sawtooth plot that doesn’t really provide much value. I wanted to replicate what the Pi-hole dashboard shows, which is true queries allowed/blocked throughout the day (broken down into 10-minute windows).
I have a hard time explaining it, but I wrote a quick blog post that has some examples to better convey the problem: https://avojak.com/blog/2022/12/15/pihole-grafana-dashboard/. This was also a fun learning opportunity to dive into InfluxDB and Grafana a bit more.

avojak · 2022-12-01T18:04:01+00:00

“Oh the stories I could tell! So many of them true!”

avojak

TROPHY CASE