Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

An Alarm Detection configuration enables you to define criteria for the generation of alarm messages. You select a condition, or combine a set of conditions, that within specific limits, generate an alarm message. To monitor the system alarms, you use the Web Interface. Note that enables you to deliver alarm messages to SNMP monitoring systems, as well.

...

The contents of the menus in the menu bar may change depending on which configuration type that has been opened in the currently displayed tab. Alarm Detection uses the standard menu items that are visible for all configurations, and these are described in the section Configuration Menus in 2.1 Menus and Buttons.

...

Item

Description

Workflow Alarm Value Names...

To to define a variable to use in the APL code, see the APL Reference Guide, and the section below, Workflow Alarm Value for further information.

...

  • A condition, or a set of conditions, see the section below, Alarm Conditions

  • An object such as host, pico instance, or workflow, that the alarm should supervise

  • The parameter that you want the alarm to supervise, for example, the Statistics value

  • Time and value limits of supervision

...

Enter a statement that describes the Alarm Detection that you are defining in the Description field.

Select the importance priority that the alarm should have in the Severity drop-down list.

...

ItemDescription

Host

Select a host server from the drop-down list

Statistic Value

Select from the drop-down list the parameter that you want the alarm to watch over. For a detailed description of every Statistic Value, see 6.16 System Statistics.

Limits

Select a limit, either Exceeds or Falls below , upon which the alarm should be triggered. Check During Last to specify the time frame during which the Limits value should be compared. If a match is detected, an alarm is invoked.

...

System Event

The System Event condition enables you to setup set up an Alarm Detection for the various Event types.

...

titleNote!

...

ItemDescription

Type

Select an event-related reason for an alarm to be invoked. For a detailed description of every event type, see 4.3. Event Types.

Filter

Use this table to define a filter of criteria for the alarm messages that you are interested in.

To define an entry, double-click on the row.

The Edit Match Value dialog box opens. Click the Add button to add a value.

Limits

See the section above, Host Statistic Value.

...

titleExample - Configuring a System Event condition

Specify the condition for the alarm to be triggered. The options are based on the number and frequency of occurrence of the event: Occurred Once, Occurred More Than, Occurred Less Than. In During Last, specify the time frame during which the Limits value should be compared. If a match is detected, an alarm is invoked.


Info
titleExample - Configuring a System Event condition


Note
titleNote!

The parameters in the following example do not apply to any specific system and are only presented here to enhance understanding of the alarm condition.


  1. Configure an Alarm Detection that applies the System Event condition.

    Configure an Alarm Detection


  2. On the Edit Alarm Condition dialog box, from the Event Type drop-down list, select Workflow State Event.
     

  3. On the Filter table double-click workflowName; the Edit Match Value dialog box opens.
     

  4. Click Add to browse and look for the specific workflow.
     

  5. Enter a limit of occurred more than 3 times during the last 24 hours.

    Select an Alarm Condition

The alarm will be triggered by every 4th occurrence of a "Workflow State Event" during the last 24 hours.

...

The Pico Instance Statistic Value condition enables you to configure an Alarm Detection that guards the pico Pico instance statistic value of a specific EC. For further information about the Pico Instance, see 6.10 Pico Viewer.

...

Info
titleExample - Configuring a Pico Instance Statistic Value condition


Note
titleNote!

The parameters in the following example do not apply to any specific system and are only presented here to enhance understanding of the alarm condition.

A telecom provider wants the system to generate an alarm if the following two events occur simultaneously:

  • The relevant pico instance (EC) memory is overloaded.

  • Too many files are open on that same particular pico Pico instance.

 

Configure an Alarm Detection
 

  1. Configure an Alarm Detection that supervises EC1 with the Pico Instance Statistic Value condition. Use this condition twice:

    • With the Used Memory statistic value

    • With the Open Files Count statistic statistical value

  2. Select the Alarm Condition Pico Instance Statistic Value.

    Select an Alarm Condition
     
  3. From the Statistic Value drop-down list, select Used Memory.
     

  4. Enter a limit of 900000 KB with - Note!- no time limit. This means that whenever this limit is exceeded, AND the other conditions are met, an alarm is generated.
     

  5. From the Alarm Detection dialog select the alarm condition Pico Instance Statistic Value once again.

    Select Another Alarm Condition


  6. This time use the statistic value Open Files Count.
     

  7. Enter a limit of 10000 files, without any time limit.

An alarm is triggered by every simultaneous occurrence of overloaded memory on EC1 AND too many open files, at any time.

...

ItemDescription

Value

Select an alarm value from the drop-down list.

Workflow

Click Browse... to enter the workflow instance(s) that you want to apply the alarm to.

Limits

Summation: Select this check box to add up the dispatchAlarmValue variable (countBillingFiles in the figure above, The Workflow Alarm Value configuration) whenever it is invoked. The Alarm Detector compares this total value with the alarm limit (exceeds or falls below) , and generates an alarm message accordingly.

Note: Selecting Summation means that the During Last entry refers to the time period during which a sum is added up. Once the set period has ended, that sum is compared with the limit value.

For All Workflows: Select this check box to add up the values (see Summation above) of all the workflows that the alarm supervises. The Alarm Detector compares this total value with the alarm limit (exceeds or falls below), and generates an alarm message accordingly. Note: This check box can only be selected when Workflow is set to Any.

For further information about Limits see the section above, Host Statistic Value.

...

The Workflow Execution Time condition enables you to generate an alarm whenever the execution time of a particular, or all workflows, exceed exceeds or fall falls below the time limit that you specify.

...

ItemDescription
WorkflowThe default workflow value is Any . Use this value when you want to apply the condition to all the Workflows. Otherwise, click Browse to select a Workflow that you apply the condition to.

...

Info
titleExample - Configuring a Workflow Throughput condition


Note
titleNote!

The parameters in the following example do not apply to any specific system and are only presented here to enhance understanding of the alarm condition.

You want the system to warn you about the detection of decreased processing rate.

  1. Configure an Alarm Detection to use the workflow throughput condition.

    Configure an Alarm Detection
  2. On the Edit Alarm Condition dialog box click Browse... to select the workflow with the processing rate that you want to supervise.
     

  3. Enter a limit of Falls Below 50000 (batches, UDRs, Bytearray).

    Configure an Alarm Condition

The alarm will be triggered by every occurrence of a workflow slowing down its processing rate to a throughput that is lower than 50000 units per second.


Scroll ignore
scroll-viewportfalse
scroll-pdftrue
scroll-officefalse
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmlfalse


Next:



Scroll pagebreak