5 ms·

One of the reason Google Analytics (and logging solutions like it) is popular is that people don't have access to server logs.

f0rfun 6y ago
You mean unpopular?
- mtmail 6y ago
  Popular. Because adding lines of javascript is much easier than processing server log files.
JackWritesCode 6y ago
Server side logs aren’t an accurate way of doing analytics and bring up compliance challenges (storing access logs and using them for purposes other than security etc.)
- hackernewsn00b 6y ago
  Can you talk a little bit more about why server side logs aren't accurate for analytics? I was planning on doing basic analytics (pageviews mostly) using Cloudfront access logs stored in an S3 bucket and queried through Athena for a site I'm working on which uses the AWS stack. I know Cloudfront logs can sometimes drop, but is there a more important reason you're talking about?
  - XCSme 6y ago
    I think with server-side only is harder to filter bots, crawlers and get accurate bounce rates or session length times.
  - tobilg 6y ago
    Shameless plug, you might want to have a look at https://github.com/ownstats/ownstats https://github.com/ownstats/ownstats
- justinclift 6y ago
  > Server side logs aren’t an accurate way of doing analytics ... Based on what? Server side logs records what the server itself sent. That sounds like it should offer far more accuracy than what a JS only solution would do. That being said, if the code for analysing the server logs is lousy, it's not going to help. :)
  - JackWritesCode 6y ago
    Before looking at accuracy, you already have compliance challenges with logging IPs / user agents and using it for analytics purposes.
    - justinclift 6y ago
      Please don't try and change the goal posts. You said: > Server side logs aren’t an accurate way of doing analytics... What is your thinking behind that statement, as it sounds incorrect?
    - ivanche 6y ago
      What compliance is challenged by logging user agents?
  - snowwrestler 6y ago
    The identifier in server logs is IP address, which is useless for distinguishing users. On the corporate side, NAT hides all the visits of many people behind a single IP. On the consumer side, ISPs change IP addresses all the time so a single person will show up as multiple IP addresses. Note that I'm just talking about distinguishing people, not identifying or tracking. A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs.
    - justinclift 6y ago
      > A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs. How can client side analytics be more accurate, when ad blockers stop visits from even being registered by client-side analytics?

f0rfun 6y ago

You mean unpopular?

mtmail 6y ago
Popular. Because adding lines of javascript is much easier than processing server log files.

JackWritesCode 6y ago

Server side logs aren’t an accurate way of doing analytics and bring up compliance challenges (storing access logs and using them for purposes other than security etc.)

hackernewsn00b 6y ago
Can you talk a little bit more about why server side logs aren't accurate for analytics? I was planning on doing basic analytics (pageviews mostly) using Cloudfront access logs stored in an S3 bucket and queried through Athena for a site I'm working on which uses the AWS stack. I know Cloudfront logs can sometimes drop, but is there a more important reason you're talking about?
- XCSme 6y ago
  I think with server-side only is harder to filter bots, crawlers and get accurate bounce rates or session length times.
- tobilg 6y ago
  Shameless plug, you might want to have a look at https://github.com/ownstats/ownstats https://github.com/ownstats/ownstats
justinclift 6y ago
> Server side logs aren’t an accurate way of doing analytics ... Based on what? Server side logs records what the server itself sent. That sounds like it should offer far more accuracy than what a JS only solution would do. That being said, if the code for analysing the server logs is lousy, it's not going to help. :)
- JackWritesCode 6y ago
  Before looking at accuracy, you already have compliance challenges with logging IPs / user agents and using it for analytics purposes.
  - justinclift 6y ago
    Please don't try and change the goal posts. You said: > Server side logs aren’t an accurate way of doing analytics... What is your thinking behind that statement, as it sounds incorrect?
  - ivanche 6y ago
    What compliance is challenged by logging user agents?
- snowwrestler 6y ago
  The identifier in server logs is IP address, which is useless for distinguishing users. On the corporate side, NAT hides all the visits of many people behind a single IP. On the consumer side, ISPs change IP addresses all the time so a single person will show up as multiple IP addresses. Note that I'm just talking about distinguishing people, not identifying or tracking. A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs.
  - justinclift 6y ago
    > A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs. How can client side analytics be more accurate, when ad blockers stop visits from even being registered by client-side analytics?