Cool! Will try it in just a minute....
--
Jarl
On 9/12/07, Geoffrey Endresen <[EMAIL PROTECTED]> wrote:
> **
>
> I don't know why it took me more than 10 years to figure out this one. The
> escalation log actually shows you if you are running late, for example if
> some escalation is taking so long that it delays others. If you never have
> had this problem they you probably have not tried hard enough.
>
> Whe the escalations are running late they create a log entry that has the
> currentime and the firetime
>
> I let the esclation log run overnight and I wanted to see how late (in
> seconds) the escalations were delayed. This works on our linux. I'm sure
> there are smart people that have solved this before, but I thought it was
> cool enough to share.
>
> % grep "set firetime of 1 second, firetime" arescl.log | awk '{print
> $23-$21, "late at", $20, $21, $22, $23, $24}' | grep -v "^0" | sort -nr |
> mail -s "late escalations report" [EMAIL PROTECTED]
>
> The output looks something like this:
>
> 1495 late at firetime 1188930731, currenttime 1188932226
> 1097 late at firetime 1188973269, currenttime 1188974366
> 1093 late at firetime 1188961114, currenttime 1188962207
> 1090 late at firetime 1188934027, currenttime 1188935117
> 1023 late at firetime 1188942394, currenttime 1188943417
>
> --
> -Geoff Endresen
> Amazon.com __20060125_______________________This posting
> was submitted with HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
