You can use inside your LogFile command like this: LogFile="/usr/share/awstats/tools/ /var/log/nginx/access.log /var/log/nginx/access.log.1.gz |" File:AWStats logo.svg from a shared repository File:AWStats logo.svg from Wikimedia Commons The following page uses this file: Software:AWStats Metadata. Detailed instructions are provided below. To do this, restore traffic usage information from logs and run the utility manually. (eg, if you rotate nginx logfiles every day at 12, but have awstats run every day at 1, then whenever awstats runs the logfile will only contain what's been written since the last rotation). You can retrieve HTML statistics for previous months using the AWstats utility.
You can then have awstats run once over this file (set LogFile appropriately).įrom then on, you should have awstats run over the most recent logfile - which is what your current configuration is doing.ĭepending on how often you are running awstats vs rotating nginx logfiles, you may want to have it read both the current logfile and the previous one.
To merge all your existing ones, run perl /usr/share/awstats/tools/ /var/log/nginx/access.log* > /tmp/nginx.tmplog The simplest thing to do is unzip all those files into a single file, then have awstats run over it once, then point awstats at your access.log file from then on.Īwstats normally has a script called, which can read the compressed files, and will merge them appropriately for awstats to do analsyis. Run the following command to setup cronjob: crontab -eĪdd the following rule: */30 * * * * root /usr/lib/cgi-bin/ -config=example.What you probably want to do here is to analyze all these logfiles once, then keep analyzing only the current logfiles from then on.
Awstats logo update#
Now you can access your AwStats by visiting the URL, Set up Cronjob to Update Logs(Optional) This new file must be stored in /home/user/publichtml/cgi-bin. The config and tally data are stored in: /home/user/domains//awstats/.data The advantage of having the data under /home/user, is that users can bring it with them when their accounts are moved around. Navigate to Web Admin at port 7080 > VirtualHosts > Name > Context, then create a CGI context with the following settings:Ĭlick the Save button and gracefully restart the web server. Ln -sf /usr/share/awstats/icon/* /var/www/html/awstats-icon Display AWStatsĪdd symlink for both cgi-bin and icons to your document root ln -sf /usr/lib/cgi-bin /var/www/html/cgi-bin In most cases, the statistics you see in AWStats will be an aggregate of the primary domain and all of the subdomains that are hosted on the same Luminate. For PLOS ONE, usage data was recorded by AWStats from Dec 20th 20 originated from the Ambra platform from Feb 2007 July 2008 was recorded. The example returns: From data in log file "/var/Phase 1 : First bypass old records, searching new record.ĭirect access after last parsed record (after line 50)įound 146 new qualified records. Verify Your AWStats Settingsīuild your initial statistics, which are generated from the current logs /usr/lib/cgi-bin/ -config= -update cp /etc/awstats/nf /etc/awstats/Īdd the following entries to /etc/awstats/ LogFile="/var/domain name and the access log path with your own settings. There is no CGI use of AWStats and static built pages are stored in a web protected realm to be securely viewed by correct allowed users only (or sent by mails). You will need to create a configuration file for each website for which you wish to view statistics.
Awstats logo install#
0 kommentar(er)
