Long-Term statistics for Pi-hole

I confirm what @MrD said and have nothing to add.

1 Like

What does FTL mean ?

btw, for the graphs, has dygraphs been considered ? For large datasets, it is the fastest dataplotter out there (even NASA is using it).

FTL - Faster Than Light

We are currently running into speed issues on the server side, not the client side, so I don't think a different client graph renderer would be much benefit (and might require some rewriting to make it work).

1 Like

Hey, new to PiHole here and really loving it.
As far as IĀ“ve seen PiHole is made for a maximum of 24 hour logging. IĀ“ve tried to disable the daily flush in cron but the results arenĀ“t convincing. The graph for "Queries over time" isnĀ“t accurate and shows (i guess) the data from the first day recorded. The "DNS Queries Blocked Todys" and all the other values are counted up correctly.

I really like the Pi-Hole project but IĀ“d like something that gives me a better long-term feedback like a hourly, daily, weekly, monthly and even yearly feedback (incl. graph) like IĀ“m used at projects like nagios. So far my querylog grows about 3MB per day which isnĀ“t too big. I think even on a minimal raspberry pi 2/3 system it could hold several weeks to months.

If this request is over the top for this tiny, damn cool and easy to use project is there a better/more suitable solution for my wishes?

You are too late, look here :wink:

Well, actually, this has been requested way earlier as well :wink:

Well, Yes and No. The current version of the Web Interface can reach its limitations even within a single day. It all depends about your number of clients and their browsing activities.

However, with the upcoming FTL engine we are able to revisit this idea. I will open a new FR for this so we have a final (?) place to discuss about this.

1 Like

I would like to see long-term statistics. I do like the simple a quick dashboard as it is but can envision a new link to history/statics. I also worry about performance (I run on a Pi Zero W) and ease of setup (I'm a Linux noob). I do have a 2nd Pi Zero W that I would be happy to test builds on (if the instructions can be dumbed down to Windows Server Admin level :smirk: )

1 Like

you could probably set up a script to output a daily api call to a csv file.

BUUUUUTTT I'm LAZY....

And really I'm a novice, so setting up scripts and doing outputs to CSV's and then graphing the data is well beyond my skills(at the moment).

Proposed beta version of the long-term statistics has two functions (so far):

3 Likes
1 Like

FTL v2.9 which includes the database has been released.

In case the database is not created and FTL shows the error:

Can't create database: unable to open database file

you have to fix permissions by doing:

sudo chown pihole:pihole /etc/pihole
sudo service pihole-FTL restart

There are daily DNS Queries "summary" would be cool if we can get the option to enable extra section of graphs that show the total DNS queries the Pihole revived

I would add:
or at least for the first two summary tiles on top make this clickable and open a querie according to the description. Example click on "DNS Queries blocked today" should open queries log filtered with blocked queries.

In the web interface, I can click status items, but get nothing,

It would be a nice addition to get some stats (especially load over time).

The "Blocked Today" et all should be clickable to get a lists.

Thanks in advance for consideration.

This may be an oversight, we don't actually store any long term stats in this regard, so there is nothing to show :slight_smile:

What would you like to see here?

ohhh... The list of domains blocked...

Being able to add multiple graphs to the home page would be great. While all DNS requests are shown in one graph, many times, I would like to be able to have another graph illustrating DNS requests for one IP in my network.

so instead of having to look at the list of IP's and then segregating that way, I can simply look at multiple graphs and quickly see one of my servers/workstations etc... or monitor one of my servers for investigation purposes.

1 Like

You should open a new feature request for this so we do not loose it out of sight.

1 Like

6 posts were split to a new topic: Problem with long term implementation