What's up with Appchkr?

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.   :-)

Integrating any Appchkr with either Slack or PagerDuty is quick and simple.  Both of these apps will accept alert emails from an Appchkr and act upon them.  The details are outlined in the Appchkrs Knowledge Base topics on Slack Integration and PagerDuty Integration in release 0.90, to come later.  Access the Appchkr Knowledge Base with the -kb option at the command line or from the 'Info' menu in the User Web Interface (UWI) in the installed program. The general idea in both cases is simply to tell those apps what you want them to do with the alert, and to create an email address in the app for the alerts to be sent to.  Then you  enter that email address as a receipient into one or more of the pertinent email address lists in your Appchkr cfg file.   That's really all there is too it.  Take those two steps and you're all done.  

The PagerDuty configuration can be a little more involved than that for Slack since there are more possible actions.  Some of these possibilities involve regular expressions to be applied against the Appchkr emails.  If you reach that point and want some help with creating those regexs let us know with a comment here, or in the support forum.  We'll be happy to offer some possibilities and to make them available to all users.  Let us know with a comment here if there are other integrations with other apps that you'd like to have, to help get more value out of your Appchkr. 

Work is advancing for the next release, 0.80, which should be out soon.  We're adding the ability to put in a custom title and subtitle for the status and uptime summary report pages so that those who wish can display these pages directly to the public, with their own brand at the top.  There seems to be a growing trend to do this, particularly for server monitoring, to build public confidence in a site a bit, and perhaps, incidentally, to reduce support calls and questions as to whether a site is up or down.    Both good things, and certainly well worth having in the more advanced Appchkrs.   The group reports are included - all four reports will have this. 

Later we'll add a some more sizzle by providing an html template to frame the reports, the ability to put logos and other images into it,  and for some degree of reformatting of the data, for an even greater level of customization and branding.   The self-refreshing branded reports served up by the UWI should ultimately provide practically everything that could be imagined and needed in this area. 

The other major thing going on is the addition of an interactive uptime history report.  This report will greatly aid and speed detecting and diagnosing recurring downtime incidents.  The interactive feature will help drilling down from a broad view to specific brief incidents in a narrow time frame.   The first stage of this report may make it into 0.80.  If not, then one of the releases shortly after that.    As with the branding it will take several releases to build the full level of functionality. 

We welcome your comments on these plans, as well as any others you'd like to contribute.