7 ms·
Webalayzer! I'm not sure there were really any other options at the time other than writing your own. Parsed the apache logs and gave you pretty detailed result
by TkTech 4mo ago
Webalayzer! I'm not sure there were really any other options at the time other than writing your own. Parsed the apache logs and gave you pretty detailed results and you could see the usage (in kb, which tells you how long ago this was!) broken down by date and IP.
Once you added a redirect rule for the IP to apache you'd just check your log and see the IP that was hitting you every couple of minutes poofed for a good few hours.
- dotancohen 4mo agoNow that's a name I've not heard in a long time. That's nuts. I suppose you had Webalayzer on a minutely cron job. It might have been drawing more resources than Apache itself!