Escalation Runtime

This program gives you an idea of how your Escalations are running. You provide it an escalation log file and it parses it apart telling you which escalations executed, how long they ran, and how many records they modified.

java -jar APLEscalationRuntime.jar -l <file> [-o <file> -s [time|pool|escalation|duration] -z -td -df “EEE MMM dd yyyy hh:mm:ss.SSS” -locale en]
l: Log File that will be analysed
o: Output File, if not specified, output is put in APLEscalationRuntime.log
s: Sort of the log file, in not specified, sorts by Escalation end time
time – Sorts by start time of the Escalation
pool – Sorts by Escalation pool
escalation – Sorts by Escalation name
duration – Sorts by duration of the Escalation
z: Suppress Zero record Escalations
td: Provide a Total Duration of all Escalations in the log file
df: Date Format: Supply the date format used in the log file. Default is “EEE MMM dd yyyy hh:mm:ss.SSS”
locale: Supply the locale for the date format. Default is “en”

Version History

2.2 – Apr 15 2019

– Fixed problem of assumed locale, the locale now defaults to en instead of machine local, if you need a different locale, please provide it in the options.

2.1 – Oct 23 2018

– Added handling of having a , instead of . in timings

2.0 – July 18 2018

– Converted it to run against 9.x escalation logs
– Removed the ‘dr’ option because 9.x doesn’t provide those details anymore
– Added a ‘WARNING’ for escalations that bump up against eachother, or are queue’d by other escalations in the same pool. It requires that you sort by pool, but will show you when you have situations where you might need to move escalations to a new pool
– Removed the arapi and log4j libraries from the download because they weren’t being used

1.3 – May 8th 2015

– added new command lines
– df – Date Format, allowing for international formats that don’t match US/English
– locale – Language the date format is in so that it knows what ‘July’ is in that language
– added support for older log formats (7.1 in the example I was given)

1.2 – Sept 4th 2014

– added ‘Total Duration’ command line parameter
– added ‘Display Requests’ command line parameter
– adjusted the output of the ‘per record’ to be included when only 1 record is modified, just to help unify the output

1.1 – Sept 3rd 2014

– Fixed output that was showing output duration in scientific notation
– Converted output timestamps to 24hr format to coincide with how Remedy logs show naturally
– Added information to the output to specify what sort was specified, as well as if it was configured to bypass zero escalations
– Added sort of ‘duration’ so that it’s easier to see which ones took the longest to execute

1.0 – Aug 30th 2014

– Initial Release

Leave a comment

Your email address will not be published. Required fields are marked *

3 thoughts on “Escalation Runtime