Edition of Friday 20 November 2026

I ran one Nginx log with 43,231 visitors through five log analyzers

Comments on “I ran one Nginx log with 43,231 visitors through five log analyzers”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

A controlled test of five open-source nginx log analyzers on a synthetic log with 43,231 known people found that unique visitor counts ranged from 49,616 to 105,885, and still differed (49,576 to 60,209) after bots were removed.

Read the original at opensource-analytics.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 29 of 140 with a score of 0.63. The panel rated it highest on new information (0.92) and substantiated (0.90), lowest on significance (0.48). Placed No. 29, No. 46 by score alone: the fourth Infrastructure & DevOps story of the day (−0.020). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Careful, reproducible benchmark of access log analyzers with a known-answer synthetic log; substantiated and practically useful for builders doing web analytics, though niche in scope.
AI judgeJudge 3gpt-5.6-luna
A reproducible synthetic-log comparison exposes how five analyzers define visitors, with commands, versions, source-backed explanations, and useful performance data. It is technically strong and actionable, though conclusions are bounded by the artificial workload.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.63total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.48
  • Reader interest0.71
  • Audience breadth0.49
  • Practical relevance0.76
  • Substantiated0.90
  • Technical depth0.87
  • New information0.92
  • Counts against: Promotional0.09
  • Counts against: Overclaim0.15

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.520.300.620.480.32+0.24+0.115
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.700.600.840.710.24+0.26+0.185
Audience breadthHow many people who build technology does it concern?0.500.500.480.490.02+0.13+0.064
Practical relevanceHow useful is it to someone who builds software or tech products?0.810.700.780.760.10+0.22+0.168
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.990.800.910.900.19+0.05+0.045
Technical depthHow technically substantive is it?1.000.800.820.870.20+0.05+0.044
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.900.980.920.10+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.040.150.080.090.11−0.19−0.017
OverclaimDo the headline or conclusions claim more than the body supports?0.180.200.080.150.12−0.11−0.017
Sum of contributions+0.633
Claim-check penalty0.000
Total, as published0.633

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #29 on Rubric, 20 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-20/29/"><img src="https://rubric.hrih.si/badge/2026-11-20/29.svg" alt="Ranked #29 on Rubric, 20 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    Across five log analyzers, unique visitor counts for the full log ranged from 49,616 to 105,885, against 43,231 real people.

    The article gives no link or citation for it.

    The article says

    “The lowest answer was 49,616. The highest was 105,885”

    The source says

    No source to compare with.

  2. No source givenNumber

    Stone Steps Webalizer ships with no robot list at all.

    The article gives no link or citation for it.

    The article says

    “the maintained fork, Stone Steps Webalizer, ships with no robot list at all”

    The source says

    No source to compare with.

  3. No source givenNumber

    As shipped, Webalizer reported 166,295 visits for a log that holds 60,706.

    The article gives no link or citation for it.

    The article says

    “As shipped it reported 166,295 visits for a log that holds 60,706”

    The source says

    No source to compare with.

  4. No source givenNumber

    On the bot-free log, AWStats reported 49,576, Webalizer 49,945, GoAccess 59,578 and Matomo 60,209 unique visitors, versus 43,231 real.

    The article gives no link or citation for it.

    The article says

    “AWStats said 49,576 and Webalizer 49,945. GoAccess said 59,578 and Matomo 60,209”

    The source says

    No source to compare with.

  5. Couldn’t checkCausal conclusion

    AWStats counts unique visitors by address per month, a weakness its glossary states plainly, which folds the 75 office workers behind three addresses into three.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The same rule folds the 75 office workers into three, a weakness the AWStats glossary states plainly”

    The source says

    No passage could be compared.

    Source cited by the article: awstats.sourceforge.io/docs/awstats_glossary.html

  6. No source givenNumber

    Matomo's overview after the full-log import showed 66,675 visits and 66,674 unique visitors, and its Returning visitors report found exactly one returning visitor despite 3,586 returning readers.

    The article gives no link or citation for it.

    The article says

    “In a month when 3,586 readers came back, Matomo’s Returning visitors report found exactly one”

    The source says

    No source to compare with.

  7. No source givenGeneralization

    On the people-only log, visits and pageviews from every tool landed within about 1.4% of the true values, while unique visitors missed by 15% to 39%.

    The article gives no link or citation for it.

    The article says

    “Visits and pageviews are the numbers you can actually compare, and on that bot-free log they stayed within 1.4% of the truth”

    The source says

    No source to compare with.

  8. No source givenBenchmark result

    Matomo's import takes over four minutes, about 43 times longer than GoAccess, while the other four tools finish in under 20 seconds.

    The article gives no link or citation for it.

    The article says

    “That’s still about 43 times longer than GoAccess”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “I ran one Nginx log with 43,231 visitors through five log analyzers”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.77

    PostgreSQL 19