Events are created within AIC through two well-defined mechanisms:
All events must be logged locally (to persistent storage) on the host where they are raised, regardless of the presence or absence of a management framework.
Every event has a fixed set of components as listed in
|Field||Auto Generated or
|Hostname||** Auto **||no||Hostname of server application runs on|
|Message||API param||no||Error description - free format null terminated string|
|Application||** Auto **||no||AIC internal federated name for the in-memory process|
|Source_Detail||API param||Yes||See Open Group Best Practices document.
Suggested examples are build revision, physical application component name (dll, binary), source file name (.c file)
|Category||API param||Yes||See Open Group Best Practices document. Used for event correlation downstream.|
|EventID||API param||Yes||Optional unique key for an event.|
|Severity||API param||no||The severity is an integer representing the level of importance associated with the event. The range of this value is 1 to 4, with 1 being the most severe and 4 being the least severe.|
|Date/Time/Zone||** Auto **||no||Internal date/time stamp including a
timezone for each event at the moment
the event is created. This stamp is in the
where XXX is the 3 character timezone.
When the internal heartbeat mechanism loses communication with
a program (and assumes the program has failed), an event is
generated with the values defined below.
|Hostname||** Auto-Generated **|
|Application||** Auto-Generated **|
|Date/Time/Zone||** Auto-Generated **|