GoAccess stats period too large

Discussion in 'Installation/Configuration' started by crycode, Jul 27, 2025.

  1. crycode

    crycode New Member

    Hello everyone,
    I'm using GoAccess to create the stats for some websites on my ISPConfig servers.
    Recently I've noticed, that GoAccess seems to create the stats always over the whole time since I enabled GoAccess stats and not for each month individually. The start date is always the day when I had enabled GoAccess and only the end date changes if I select an other month the top "Jump to previous stats" select.
    Currently I'm running the latest ISPConfig 3.3.0p2 on Ubuntu 24.04 with nginx. Looking back in my created stats it seems this behavior always existed since my stats of each month start hat the same day in may 2024.
    Example:
    Screenshot 2025-07-27 162136.png Screenshot 2025-07-27 162001.png

    I've already created a new test website and enabled GoAccess for this site to compare the generated goaccess.conf file in the log dir of the website, but there seem to be no differences. Also tested on a second server with the same behavior.

    I can't imagine that this is the intended behavior.
    Any idea how to fix this and get monthly stats with GoAccess?
     
  2. michelangelo

    michelangelo Active Member

    The only way to achieve what you want would be if ISPConfig would rotate the GoAccess DBs every month, which it doesn't right now.
    Assuming ISPConfig would do that, you would lose access to the historical data because current GoAccess doesn't provide any options to merge its DBs at a later point again.

    However, there is a feature request in the GoAccess Bugtracker on Github so that it's possible to aggregate the visitors by month but there seems to be currently no further development regarding this issue.
    See: https://github.com/allinurl/goaccess/issues/139

    So the only options we have is either to hope that the GoAccess developer will provide a way to merge the GoAccess DBs, because if not, we will rather likely end up with a historical dataset that can't be unified to one GoAccess database again, or having issue #139 implemented.

    I personally tend to have the GoAccess issue #139 implemented.

    When in doubt whatsoever, there is also Matomo which can be also fed with Webserver log files. Only downside is, that this statistic tool is not natively supported by ISPConfig and it would require a manual setup by the admin.
     
    crycode and till like this.
  3. crycode

    crycode New Member

    Thank you! So it's currently the somewhat expected behavior.

    Too bad that this seems to have a low priority at GoAccess.

    I'll have a look at Matomo, thanks for this tip!
     

Share This Page