Table of Contents

General Executable Properties

The General tab, found in the Template, Report and Constant Delivery Pipeline property views, contains name and schedule properties.

  • Use the Name text box to specify a unique name.
  • Use the Auto-Generate Name Auto Generate Name Button button to generate a name based on the object's properties.
  • Use the Enabled check box to schedule execution of this object.
  • Use the Re-enable check box to configure the software to automatically re-enable disabled objects once the configured period has expired.
  • Check the Restart options to automatically restart monitors and reports that are executing when the service is restarted.
  • The Select Schedule drop-down includes a drop-down button and a plus button. For more information see: Schedules
  • Use the Drop-Down button to select an already existing schedule.
  • Use the Plus button to add a new schedule to the system.

  • Some templates enable you to specify a retry schedule when the associated monitor is triggered or errors. Use the Retry Schedule drop-down to schedule the frequency to re-run the monitor until at some future time the monitor recovers from the triggered state or the triggered state is cleared.
  • Some templates enable you to specify a failure rate. The failure rate enables you to require a set number of triggers or error over a period of time prior to triggering actions. Use the Failure rate controls to enable and set the number of triggers or errors that must occur with a period of time.
    Information A use case for this option is found in the default settings of the Ping Monitor Template. Since ping tests regularly fail, with an execution schedule of every 5 seconds this option is set to require 3 failures within 20 seconds. This configuration minimizes or even eliminates false positives by deferring the trigger 10 seconds after the first failure for a total time of 15 seconds.
  • Use the Retain history option to specify the length of time to retain execution history and results.
    Information When monitoring CPU every minute, for example, you may want to consider setting the range to a lower number such as 7 days so the history view can quickly display while also removing data no longer needed. When downloading and saving Event Logs consider setting the value to something larger such as 6 months so an audit trail is left behind.

Related Topics

Schedules

Templates

Reports

Auto-Configurators