HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
eldy
AWStats
Perl2019–2025
eldy / AWStats

AWStats

AWStats Log Analyzer project (official sources)

6Distinct people
7Mentions
0Explicit recommenders
439GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

AWStats Log Analyzer project (official sources)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2019-05-11 08:13:23 UTC to 2025-08-30 12:29:01 UTC.

01232019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

3 sources
Based on your requirements it sounds like AWStats [1] may be a fit. It's rather old-school but it's simple and works great on access logs and can be run on any node that you consolidate your logs to. It's had a sketchy security history so run it on something only you can access and/or put decent authentication in front of it. Some Linux distributions include AWStats as a package in their repositories. [1] - https://github.com/eldy/AWStats
In Ask HN: Which tool for log aggregation on self-hosted web server?
I don't know if many still use it but AWStats [1][2] is one of the oldest self hosted solutions. I used it ages ago. It uses access logs vs. other platforms depending on javascript being embedded in pages. It's had some vulnerabilities in the past so it should be protected by authentication. It depends on Perl and a web server that supports CGI scripts. Stats processing is done in cron against the access logs so there is no added load based on page visits. It could even be run on a separate machine/node that logs are aggregated to. Part of the installation is configuring which log format your servers use. If using a non standard format one can map the related fields. If configuring AWStats to perform reverse DNS lookups I would suggest also installing Unbound DNS specifically on that machine and setting the following in /etc/unboun
Read the rest
d/unbound.conf to minimize load on your upstream servers perhaps even higher: cache-min-ttl: 86400 cache-max-ttl: 1209600 serve-expired: yes serve-expired-ttl: 259200 serve-expired-reply-ttl: 30 serve-expired-ttl-reset: yes val-bogus-ttl: 600 cache-max-negative-ttl: 86400 serve-expired-client-timeout: 1800 The above is specifically for machines dedicated to looking up a very large number of PTR records, not for a home router. Some DNS providers rate limit mass-lookups of IP addresses. PTR records are slow to change so a high TTL override on a log processing box is generally fine unless you care about short lived PTR records AWS, Azure, etc.. [1] - https://awstats.sourceforge.io/ [2] - https://github.com/eldy/AWStats
In Ask HN: Alternatives to Google Analytics in 2023

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.