[Catalyst] Monitoring Catalyst on Apache2 & FastCGI

[Robert Brown]

Are you using https://metacpan.org/pod/Catalyst::Log for your own 
application-level logging?

This would be step one.

For performance testing, memory leaks, etc. I'm sure there's plenty of 
options on CPAN?



On 05/05/2014 11:41 AM, Bernhard Bauch wrote:
> Dear all,
>
> I'd need some help with debugging and monitoring an apache2+fastcgi
> production environment ...
> ... i did not find any information about that online ?! :(
>
> what i would need is logs of the fcgi processes that show:
> * the request IP, url and paramters
> * how long it took to answer a request
> * cpu+mem usage of each process
>
> putting a catalyst application into Debug-mode is one option;
> but thats not clever for a production environment ... and its pretty
> hard to scan through all that information.
>
> any ideas ?
>
>
> the story behind....
>
> We are running a bunch of Catalyst applications in an Apache2 and
> FastCGI production environemnt.
> Since a few days it happend 2 times, that one of these applications ran
> really "hot";
> the fcgi processes of that application used 4times more ram and constant
> high CPU-usage.
> the result was, that apache spanned lots of processes trying to answer
> all requests;
>>>> so at the end *all* requests to apache2 returned a "timeout" ..
> i tried to find out what the problem was; grubbed through lots of apache
> access logs without any reasonable result :(
>
> i'd be thankful for any hints how a catalyst+apache+fastcgi environment
> can be monitored ..
>
> thanks alot,
> bernhard
>
>
>
>
> _______________________________________________
> List: Catalyst at lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scsys.co.uk/pipermail/catalyst/attachments/20140505/e29755bd/attachment.htm>