Request: Statistic reset

TschernoBill · February 11, 2020, 9:09pm

Please follow the below template, it will help us to help you!

Please ensure that you are running the latest version of the beta code.
Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.

Problem with Beta 5.0:

Debug Token:

Is it possible to add a (safe) function to reset the ftl-statistics? While searching for it I only found a solution by deleting the old database.

An example where this is usefull: Getting a exact view on the summary after deleting or deactivating an upstream-DNS.

Thanks in advance to all of you for the awesome work!

DL6ER · February 15, 2020, 5:27pm

You could try

sudo service pihole-FTL stop
sudo sqlite3 /etc/pihole/pihole-FTL.db "DELETE FROM queries WHERE timestamp > (cast(strftime('%s', 'now') as int))-24*60*60"
sudo service pihole-FTL start

This will selectively remove the last 24 hours without destroying the entire database.

yubiuser · June 1, 2020, 9:28pm

I think this would nicely fit into the "Danger Zone!" in Settings/System

jfb · June 1, 2020, 10:38pm

I don't agree. This is not a frequently performed task and generally falls into the "edge case" category. Adding code for this occasional use is not warranted, in my opinion.

yubiuser · June 2, 2020, 6:15am

How often do you press "Flush logs" or "Disable query logging"?

yubiuser · August 4, 2020, 4:06pm

Flushing logs does flush the long-term database, but only the last 24h. This seems a bit counterintuitive - why does it flush at all (not not just the logs) and why not all data?

github.com

pi-hole/pi-hole/blob/56cd7c4d59ceb629a2170cd1c8ab78ef26366019/advanced/Scripts/piholeLogFlush.sh#L60


        /usr/sbin/logrotate --force /etc/pihole/logrotate; sleep 3
        /usr/sbin/logrotate --force /etc/pihole/logrotate
    else
        # Flush both pihole.log and pihole.log.1 (if existing)
        echo " " > /var/log/pihole.log
        if [ -f /var/log/pihole.log.1 ]; then
            echo " " > /var/log/pihole.log.1
            chmod 644 /var/log/pihole.log.1
        fi
    fi
    # Delete most recent 24 hours from FTL's database, leave even older data intact (don't wipe out all history)
    deleted=$(sqlite3 "${DBFILE}" "DELETE FROM queries WHERE timestamp >= strftime('%s','now')-86400; select changes() from queries limit 1")
    # Restart pihole-FTL to force reloading history
    sudo pihole restartdns
fi
if [[ "$@" != *"quiet"* ]]; then
    echo -e "${OVER}  ${TICK} Flushed /var/log/pihole.log"
    echo -e "  ${TICK} Deleted ${deleted} queries from database"
fi

DL6ER · August 4, 2020, 4:20pm

Because it involves an FTL restart. And FTL would re-import the history when it would still be in the database. The net effect would be that everything looks to be still there.

Because this was originally meant more in a "I want to hide some things happened recently" way. Very much like browsers offer you to delete the data only partially (without loosing everything). I can see that there may be a need to get both. However, flushing the entirety of the logs can easily be obtained by deleting the database. Flushing it only partially is a bit more involved as you need an SQL instruction.