Edward Ned Harvey (lopser) wrote: > I want to know if a web server gets overrun by too much traffic requests.
First you need to define "overrun." Not for the mailing list, but for yourself. > I'm looking for something that knows how to process the logs of . . . Assuming you want to know of the problem when it happens and not hours (or days or weeks later), I believe the current best practice is to monitor the response time of the system by sending it actual web requests from an off-host box (and measuring the response time on that same box). Once you know the system isn't performing according to your SLA, then you can look in the logs (using any number of tools) to see if there's any indication why the system is failing. > I'm looking for something more specific than monitoring and alerting Um, what is this if it's not monitoring? Adam _______________________________________________ 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/
