How the Knowledge Base classifies incoming events

When the event is collected by the cell, the cell compares the incoming event to the predefined event classes in the Knowledge Base to determine the event type of the incoming event and validate the event.

If an incoming event does not match one the predefined event classes, the cell performs one of the following actions:

•  If the event does not match any of the predefined events in the KB at all, an internal event in the form of an error message is generated and the event is stored as an MC_CELL_UNDEFINED_CLASS event with a MINOR severity and a slot, class_name, containing the original, incorrect event class. 
• If the event is of a class that matches one of the predefined event classes but contains undefined event slots, the event is generated and continues to processing, but incorrect slot names are stored in the mc_bad_slot_names slot, and the corresponding values are stored in the mc_bad_slot_values slot. 
• If the event has slot(s) that contain value(s) that cannot be interpreted (for example, alphabetical string data in an integer slot), the default slot values are used, the incorrect slot names are stored in the mc_bad_slot_names slot, and the values of the incorrect slots are stored in the mc_bad_slot_values slot. 
• If an event cannot be parsed, an internal MC_CELL_PARSE_ERROR event is created containing the text for that event stored in the event_text slot. The MC_CELL_PARSE_ERROR event also uses error_line, error_column, and error_messages slots to indicate the position in text where the error occurs and the parsing error message. The MC_CELL_PARSE_ERROR event has a default severity of MINOR.