[GRLUG] Process timing

[Grand Rapids Linux Users Group]

correction. 

nagios is cool, but not what i meant. 
munin is what i was thinking of

both excellent sources of infinite perl wisdom too


-j





> On Aug 17, 2020, at 6:07 PM, Grand Rapids Linux Users Group <grlug at grlug.org> wrote:
> 
> no proc!!! no wae!
> prolly in /run or some such magic ヽ(｀Д´)⊃━☆ﾟ. * ･ ｡ﾟ,
> 
> apache has mod_status which provides a lot of info about the server, threads/workers & requests/response timing
> 
> enabling it is simple, but do ensure you’ve paid attention to Allow From 127/0 and such. you don’t wanna give us all those spicy bits.
> 
> tools like nagios can help spruce up the display, but you might get by with the default look-n-feel
> 
> 
> 
> -j
> 
> 
> 
> 
> 
>> On Aug 17, 2020, at 6:01 PM, Grand Rapids Linux Users Group <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>> 
>> On Mon, 17 Aug 2020, Grand Rapids Linux Users Group wrote:
>> 
>>> watch proc topless
>>> 
>> Interesting, .. unfortunately no proc on this distro.
>> 
>>> execution time and process/thread life are not the same tho, so if
>>> you’re tryna see how long a script executes, you might actually find
>>> apache’s LogFormat helpful, but not as great as nginx.
>>> 
>> Most of the timing information is there in the logs, .. but what/how to
>> parse?
>> 
>> 	Thanks!
>> -- 
>> grlug mailing list
>> grlug at grlug.org <mailto:grlug at grlug.org>
>> https://shinobu.grlug.org/mailman/listinfo/grlug
> 
> -- 
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200817/2d418c02/attachment.html>