Performance impact of recurring wait time, repeatable triggers in a monitor model

Technote (troubleshooting)


Problem(Abstract)

A low recurring wait time interval (for example every 1 minute) for a trigger defined in a monitor model monitoring context will result in frequent trigger evaluations, which might cause event processing performance problems under high volumes of active instances.

Additionally, if the trigger is repeatable and there is an associated notification alert, you might receive excessive notifications. The high number of notifications can cause the high message threshold to be exceeded for the ActionManagerQueueDestination, resulting in further problems.

Resolving the problem

Consider the following options when defining a recurring wait time trigger in a monitoring context:

  1. Use a longer "recurring wait time" duration.
  2. Clear the "Trigger is repeatable" option for the trigger, if not needed.
  3. Use a longer "recurring wait-time checking interval" in the runtime configuration for the monitor model on the Monitor server.


Refer to the Related information section below for further information.

Related information

Modifying the runtime configuration of a model
Defining triggers for monitoring contexts
Defining triggers for KPI contexts

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Monitor
Performance

Software version:

6.1, 6.2, 7.0

Operating system(s):

AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows

Reference #:

1413995

Modified date:

2009-12-10

Translate my page

Machine Translation

Content navigation