Saturday, 06 July 2019

The Uptime History Report is now available.

The Uptime History Report, alluded to in an earlier post, is now available as part of release 0.90, just out.  This is a graphical report intended to be used interactively to zero in on areas of downtime of interest for rapid troubleshooting.   It makes it possible to quickly establish that there is a pattern of repeated downtime at a uniform interval for a target or group, or that simultaneous downtime is occurring on some set of targets, suggesting a common cause, among many other possible uses.   There is one up/down histogram per target or group with a common time scale, and with multiple targets on one page.  One simply narrows the time period around an area of interest to expand the scale and see more detail, until the question at hand is answered by the graphs, in almost no time.  The raw data for the report is updated in realtime, like all the other Appchkr reports, so the uptime history can also be followed graphically in realtime if desired. 

This report, and the raw data file it uses, are a substantial addition to Appchkr functionality, so the release number has been bumped from 0.82 to 0.90 to reflect that fact.   Releases 0.83 - 0.89 have been skipped.   The report and raw data file are available in the three leading Appchkr types (appchkr, networkchkr, and serverchkr), but not in the five specialty types.  As always, any Appchkr type may easily be upgraded to a higher type, at any time, with little effort.

Having the file of the raw uptime data also makes it possible to keep long term uptime records in a database or file if desired.  Custom uptime/downtime reports can also be generated from the file using spreadsheets or other reporting programs.  The details of the raw data format are given in the 'Advanced' part of the Appchkr documentation incorporated into the release, under the topic 'Uptime Raw Data Format'. 

The report can be run from either the command line or the User Web Interface (UWI) or both, like almost all of Appchkr.   This version does not handle AlertOnUp targets ideally though, but the fix for that has been postponed since those are rather uncommon.  It can be fixed in the future if there is enough demand, along with a few other minor enhancements that are under consideration.  Let us know your preferences.   :-)