StoreGazer Alert File Definitions

StoreGazer 4690 Alert File

The alert file contains file, process, and utilization definitions that EDJAgent will monitor. If any of the alert definitions fail, an alert will be sent to the StoreGazer Server with the provided priority (Low, Medium, or High). If no priority is provided, the alert will default to Low. If the issue resolves itself, a second alert will be sent notifying the Server that the alert is no longer outstanding. A resolved alert will be displayed within the Client, although it will appear in a ghosted state.

An alert can also contain a list of actions to execute, similar to the event file

Common Alert Parameters

The following table contains the common alert parameters. These parameters are accepted across all alert types (file, process, and utilization).

An identification number used in distinguishing alerts from each other [Range: 1 to 999]. This parameter always appears at the beginning of a new alert, and is easily distinguished from all other parameters since it must be contained within brackets.

The ID of the controller that should monitor the alert. If this parameter is left out of the alert definition, all controllers will monitor the alert. There are several wildcards that can be used in this field:

  • AA – Monitor the alert on the acting master.
  • AB – Monitor the alert on the acting alternate master.
  • AC – Monitor the alert on the acting file server.
  • AD – Monitor the alert on the acting alternate file server.

This parameter can be used in multiple ways

  • If the frequency is set to 0, this parameter is used in conjunction with the ‘Start/Stop Time’ parameters. If the alert conditions are not met within the provided start/stop times, the alert will be raised.
  • If the frequency is greater than or equal to 1, it will be used along with the ‘Interval’ parameter. If the alert conditions are met a defined number of times (frequency) within a defined period of time (interval), the alert will be raised.

If the alert does not resolve itself, it will be logged every ‘Interval’ minutes. This parameter can also be used in conjunction with the ‘Frequency’ parameter to check if the alert conditions are met defined number of times (frequency) within a defined period of time (interval), the alert will be raised.

The Start/Stop Time fields can be used to place time restrictions on alerts. The times can span midnight and are formatted for military time with no separators. Depending on the presence of the ‘Frequency’ and ‘Day’ parameters, the Start/Stop Time fields can be used in multiple ways.

  • If the ‘Frequency’ parameter is non-existent or if it is greater than 0:

    If the specified alert conditions are met between the provided Start and Stop times, the alert will be raised. Otherwise, the alert will be ignored.

  • If the ‘Frequency’ parameter is set to 0:

    If the specified alert conditions are not met between the provided Start and Stop times, the alert will be raised as soon as the time expires.

  • If the ‘Day’ parameter is used:

    The ‘Day’ parameter can be used in conjunction with either of the above cases to specify a specific day of the week for the alert to be examined.

This parameter can be used to indicate the day(s) of the week that an alert should be monitored. The possible values are Sun, Mon, Tue, Wed, Thu, Fri, and Sat.

This parameter can be used to specify the date(s) that an alert should (or should not) be monitored. The dates should be provided in a comma-delimited list in mm/dd format. An ‘X’ may precede the date if date exclusion is required.

The priority can be set to High, Medium, or Low. The priority setting determines how the alert is displayed in the StoreGazer Client Alert Monitor (Red, Orange, and Yellow icons).

A list of actions to execute if the alert is triggered.

A boolean field that determines the following:

  • True [Default] – Send an alert message to the defined StoreGazer Server(s).
  • False – Do not send an alert message. Instead, only performed the defined action(s)

The following alert types are supported:

  • Process – Used to monitor 4690 applications.
  • File – Used to monitor 4690 files.
  • Resource – Used to monitor 4690 system resources (CPU, Memory, and Disk).


Type-Specific Alert Parameters

The sample alert file that ships with the StoreGazer 4690 installation package contains descriptions for the type-specific fields recognized by StoreGazer.