Having issued these declarations, the monitor will thereafter take notice of these events, remembering them in its database of events, and allowing the definition of further events in terms of these external events. Logical combinations of events can be defined. If an event is defined in terms of other events that themselves have parameters, then there will be a variety of ways in which those parameter values can be used. Our experimental user-interface for FLEA makes the task of defining events such as the above a simple matter. To see further details, click here .
Sequences of events are often useful to define.
Note that the RemoveLicense event need not be the very next event following AddLicense - there may be any number of other events intervening between an AddLicense event and a RemoveLicense event, and an AddThenRemoveLicense event will still be recognized as having occurred. Generally, the time of a defined event should be the earliest time at which that event can be determined to have occurred. Just as was the case with logical events, if an event is defined in terms of a sequence of other events that themselves have parameters, then there will be a variety of ways in which those parameter values can be used. A user is added, then later that same-named user is removed. The AddThenRemoveSameUser event is defined to have the name of that user as its parameter.