Halcyon Custom Task Monitor allows you to run a command at specified intervals, defined at Group level, within day and time constraints.

This allows you to use Custom Task Monitor to act as a simple Job Scheduler and also to extend Halcyon's monitoring in to new areas - and all backed up with the comprehensive Halcyon alerting and automatic corrective action functionality.

Defining the Run/Check Interval
The Custom Task Monitor allows you to define the interval and a time range when to perform the run/check at Group level:

Defining the Run/Check Interval

Within each Group you can define multiple Rules which allow you to define the days and the time range for the run/check. Combined with the Group this provides a scope of days, time range and frequency:

Defining the Days and Time Range

Preventing further Runs/Checks if something goes wrong                                                                                                          

By use of "Suspend on alert" on the Rule you can prevent a further run/check for a period of time if something goes wrong:

Suspend On Alert Settings

Defining the Command to be run and the corrective actions on error

Within the Rule you define the command to be run and also which actions to perform if there is a problem*:

Defining the Command to be run

 If something goes wrong* you can define automatic Actions to be performed with any combination of:

  • Ignoring the problem (not recommended!)
  • Running additional commands.
  • Sending an Alert to the Halcyon Enterprise Console, a graphical color-coded dashboard.
  • Sending an Alert to the Halcyon Enterprise Console iPhone and/or iPad app, a graphical color-coded dashboard.
  • Sending an Alert to an IBM i message queue, such as QSYSOPR.
  • Sending an Alert via email to multiple recipients, with full support for Rotas and Escalations.
  • Sending an Alert via SMS to multiple cell phones or smart phones, with full support for Rotas and Escalations.
  • Sending an Alert to other systems via use of SNMP.
  • Sending an Alert to an external file on the IBM i.
  • Stopping future runs/checks.
  • Enabling future runs/checks of another Rule.

* A problem/error is determined by the command returning a message with Severity 30 or greater.

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: April 03, 2019