![]() ![]() It’s something that has to be done on the backend, on the logs side. ![]() One of the most obvious choices for this kind of work is to use Google Analytics - unfortunately, this means that it will only work if it’s not blacklisted from the user side - that includes NoScript users and of course most of the spammers. It’s even more bothersome when you consider that there is no way to reconsider the already analyzed data, if a new URL is identified as a search engine, or an user agent a bot. Things like Android versions and other fringe OSes would be extremely useful for me, but adding support for all of them is a pain and I have enough things on my plates that this is not something I’m looking forward to tackle myself. It doesn’t filter referrers search engines as much as it used to be (it’s still important to filter out requests coming from Google, but newer search engines are not recognized), and most of the new “social bookmark” websites are not there at all - yes it’s possible to keep adding to them, but with upstream not moving, this is getting harder and harder.Įven more important, for my ruleset work, is the lack of identification of modern browsers. It used to work nicely, but nowadays it’s definitely lacking. Awstats vs piwik generator#To do so, I’ve been using for, at this point, years, AWStats which is a Perl analyzer, generator and CGI application. This is especially useful at the start of the month to identify referrer spam and other similar issues, which in turn allows me to update my ModSecurity ruleset so that more spammers are caught and dealt with. You probably don’t know that, but for my blog I do analyse the Apache logs with AWStats over and over again. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |