~~CLOSETOC~~
<html><font color=#3399f3 size="+2"><b>System Event and Threshold Actions</b></font></html>

   
Each Service Application Engine supports a range of System Events ((Events that occur as result of some internal engine operations)) and event Thresholds ((Settable limits.  When a threshold limit is crossed a System Event is raised.)) that allow users to observe and react to system-level conditions that can occur inside the runtime.  

System Events are raised with a GLOBAL event scope.  They are visible to all clients across all nodes in an application engine Sysplex.  As such, care must be taken when subscribing to system events.  When using wild-card filters and electing to receive a broad range of data the client can easily create a stream of events that will flood the network and overwhelm the CPU.  For best results filters should include Event Source information that limits the source to several nodes or a particular type of event.

=====System Events=====

====Event Types====

====Creating Historical Data====

====Trending and Usage Analysis====


=====CPU Usage Monitoring=====

====Monitoring Events====

====Setting Thresholds====

====Reacting to CPU Usage Events====


=====Memory Usage Monitoring=====

====Monitoring Events====

====Setting Thresholds====

====Reacting to Memory Usage Events====


=====Thread Deadlock Monitoring=====

====Monitoring Events====

====Reacting to Thread Deadlock Events====


<html>
<img src="/dokuwiki/_media/icons_large/bowlerhat-transp.png" alt="Smiley face" height="46" width="46" style="margin-left:-6px;">
<a href="/dokuwiki/start" style="margin-left:-1em; font-weight:bold; color:#990000">Back</a>
</html>