IBM Support

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

Troubleshooting


Problem

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.

[{"Product":{"code":"SSSRR3","label":"WebSphere Business Monitor"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Performance","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;6.2;6.1","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
23 June 2018

UID

swg21413995