It would be nice if Deos supplied apps could log information that status monitor/timemap could know about. Currently logSystemEvent will always use the enumeration user_defined_event and there is only a 32 bit data field to differentiate. Therefore apps and shared libraries may conflict with the interpretation of this field and status monitor cannot assume a user_defined_event came from a Deos library.

One proposal would be to extend the execution_history_t enumeration to have lots of user defined events. This is a 32 bit value with under 100 values currently assigned. We could define many spares for kernel growth and then a large range of user defined events. A portion of this range can be documented for Deos supplied apps/libraries and a portion for user apps. Then we could have a new API:
logSystemEventEx(execution_history_t event, DWORD data);
logSystemEvent could be deprecated, but would maintain backward compatability by continuing to use user_defined_event as the event.

This allows the supplied apps to log a full 32 bit data value, using separate enumerations to distinguish the events. An example is the 653 runtime which logs several different types of events and would like to associate the 32 bit 653 process id or other data with the event.