Versions Compared

Key

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

...

Note
titleNote!
  1. An alarm is generated only if ALL conditions in the Alarm Detection are met.
     

  2. The Alarm condition limits are reset:

    • Every time you restart the Platform

    • Every time you save the alarm configuration

    • When you resolve the alarm

    Alarms can be managed in the 1.2.3 Alarm Inspector Tab web interface.

The Alarm Conditions that you can choose from are:

...

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 ValueSpecify 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.

...

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 on 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