An event is a means of identifying a change of state of a process or device on the network, so that a notification of the change can be generated and tracked.
For example: an event identifies when a workstation changes from online on the network to offline, or when a critical resource threshold, such as virtual memory utilization, is met.
%ProductName% uses the following criteria to identify the characteristics of an event, such as its origin, cause, and severity.
Events that are generated as a result of monitoring a group of systems are called Group events. Events that are generated as the result of monitoring one or more individual systems are termed Individual events. Refer to Understanding How Group Events and Individual Events Are Interpreted for more information.
Actions define the steps to take in response to an event, for example, entering the event in the event log, sending a message that includes the text of the event, or executing a command. Actions that can be taken in response to an event are created using the predefined action templates described in Understanding Event Action Plans.