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
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 p
Here at $WORK we have a distributed Web Filtering system. We have just
started looking to streamline the process. I figured that other large
school districts have done this already or attempted it so I will ask here.
We have 18 High Schools and 140 Elementary schools. The Filtering is local
but ma
There's something else you should consider at the same time. There are
many ways that you can setup connection throttling such that the web
server is prevented from being overrun in some of the more obvious ways
that you might not want. There are plugin modules for bandwidth
limiting, but you c
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 wan
