Yes, Ben is correct. To see the results before the AWK just to this: grep "set firetime of 1 second, firetime" arescl.log
On 9/12/07, Ben Chernys <[EMAIL PROTECTED]> wrote: > > Guys, > > Read the script. It is the awk script that prints the text "late at" so > no greps will find it in the escalation log (unless you have an escalation > named ...late at...) > > Cheers > Ben > > >----- ------- Original Message ------- ----- > >From: "Fariss, Ron" > ><[EMAIL PROTECTED]> > >To: arslist@ARSLIST.ORG > >Sent: Wed, 12 Sep 2007 10:39:03 > > > >Frederick, > > > >Ok, probably a dumb question, but are you sure that > >your Escalation > >Logging is turned on and if it is, that the name of > >your escalation log > >file is aresc.log. Mine happens to be aresc2.log. > > > >Ron Fariss > >AIG Global Services > >Service Desk Automation > >713-831-2365 (Office) > >281-782-0979 (Mobile) > > > > > >________________________________ > > > >From: "Action Request System discussion > >list(ARSList)" > >[mailto:[EMAIL PROTECTED] On Behalf Of "Grooms, > >Frederick W" > >Sent: Wednesday, September 12, 2007 8:07 AM > >To: arslist@ARSLIST.ORG > >Subject: Re: cool awk script to find out how late > >escalations are > >running > > > > > >** > >What version are you on? I just tried doing a > >grep -i "late at" > >aresc.log and it did not pull up anything even > >though I know I have > >escalation delays. > > > >I am on ARS 6.3 patch 20 on Solaris 9 (w/ Oracle > >10g) > > > >Fred > > > >________________________________ > > > >From: Action Request System discussion > >list(ARSList) > >[mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey > >Endresen > >Sent: Tuesday, September 11, 2007 5:10 PM > >To: arslist@ARSLIST.ORG > >Subject: cool awk script to find out how late > >escalations are running > > > > > > > >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" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > -- -Geoff Endresen Amazon.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
