Escalation Timeline


This is a program which will connect to your remedy server and grab the escalations you specify and generate two outputs,
one visible through an html page that will show you an interactive timeline of your escalation firing patterns, and another
in csv format that you can do with what you want. If you are running ITSM, or have a report with a high number of escalations
and execution times, you may want to peruse the CSV file instead of the html file as it’ll take awhile to render and be hard
to understand the output

This program offers either command line, or config file operation, here are the options if you need to use them

Syntax:
All command line options are optional, those listed as required are required to exist either in the command line or the config file Command line overrides config file in all situations

-h/? This syntax message you are reading
-c Config file to use for configuration, if unspecified it uses APLEscalationTimeline.properties (Optional)
-x Name or IP of Remedy server to connect to (Required)
-t TCP Port to connect to, if not specified a value of 0 is used (Optional)
-u Admin user name used to connect to Remedy server (Required)
-p Password for the Admin user (Optional)
-s Start Date for the execution, if not supplied it is assumed today (Optional)
-d Duration in days that you want it to calculate the timeline out to, defaults to 7 days if not supplied (Optional)
-type [BOTH|TIME|INTERVAL] If not supplied it defaults to TIME (Optional)
BOTH: Plots both Time and Interval based escalations onto the timeline
TIME: Just Time based, is better to use this option if you plan on using a long duration
INTERVAL: Plots just the Interval based escalations, and assumes the start time is ‘base’ and goes from there, recommend using short durations if using this option
-v Verbose, displays details of which escalation it’s working on a the moment
-output Prefix of what you want the output name to be, if not specified is APLEscalationTimelineOutput
-pool Specifies the pool to report on, if left blank it’ll report on all pools

I’m using the opensource timeline simile project and requires access to the internet to grab the libraries from them. ¬†If you wish to run this in a ‘closed’ environment, you will need to pull all of that stuff locally and update the template¬†file to run locally instead of from the internet.

This program is written to connect to your Remedy server, but the output can be run locally on your machine not requiring a web server to view the output

1 – Edit APLEscalationTimeline.properties to be related to your system
2 – Double Click on the Jar file to execute the program
4 – Open the files in the output diretory to view the results

Version History

3.0 – Apr 21 2020

  • Fixed long standing problem with duration that was causing way more data than expected to be created
  • Modified CSV output to be sorted by execution time, then pool, then escalation name for easier reading
  • Added pool configuration to allow you to report on single pool if desired
  • Removed Offset configuration because it’s not working the same in 9.x as it was in 8.x

2.5 – Mar 30 2015

  • Added feature to be able to set interval to hours instead of minimum of days

2.1 – Mar 16 2015

  • Fixed small bug that was causing a null pointer exception on some servers

2.0 – Mar 22 2014

  • Removed the need for a batch file by providing an executable JAR File, although all command line parameters are still supported
  • Restructured the folders a bit to be less confusing
  • ‘branded’ the tool to be part of the Programming Legacy family of tools
  • re-compiled against Java 1.6 as someone reported an error running it because it was compiled against a newer version
  • found that the simile project moved homes, update the template to pull from the new home

1.5 – Jan 23 2012

  • Re-structured the code to be a bit more proper
  • Added significant error handling and reporting capabilities to help explain errors better if they occur
  • I didn’t add any new functionality (because none was asked for), but I did implement my better understanding of Java that I have acquired over the last two years
  • Updated program to use 7.6.4 API instead of 7.5

1.01

  • Fixed program so that it generates the data for ‘this’ month instead of ‘this – 1’…the month is 0 index based instead of 1, never noticed in my local testing
  • Added ability to specify config file on command line
  • Added ability to create copy of files with ‘output’ option, this copies the esc_timeline.* files to a new fileset so you can generate server specific sets
  • Added offset function to convert from GMT to local time
  • Added verbose option to display the processing of escalations in detail
  • Added csv file to the output so that you can do what you want with the data

1.0 – May 31 2010

  • Initial Release


Leave a comment

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

2 thoughts on “Escalation Timeline