Personally, I'd look into parsing the mod_status output first. Access logs tend to grow quickly, so that's a lot of reading.
logstash might help you make sense of all kinds of logs. Best, Hans NL On Fri, Aug 21, 2015 at 3:10 PM, Edward Ned Harvey (lopser) < lop...@nedharvey.com> wrote: > I want to know if a web server gets overrun by too much traffic requests. > I certainly know how to monitor memory, and tweak the MPM and stuff in > apache config files, but I assume if it runs out of threads or memory or > anything, it will throw errors into the log file, which are immediately > buried. > > > > I can definitely figure this out, but I know I definitely shouldn't. It's > already been done. > > > > I am familiar with zabbix and spiceworks and other monitoring systems. I'm > looking for something more specific than monitoring and alerting - I'm > looking for something that knows how to process the logs of apache > specifically, and mysql, and whatever other services we're using. So I'm > looking for log processing. > > > > Something out there already knows how to process all the log files, > including the apache logs, and tell me the important stuff. > > > > How's it done? > > > > Thanks... > > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ > >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
