{'fraction_non_alphanumeric': 0.018410041841004185, 'fraction_numerical': 0.0, 'mean_word_length': 4.920792079207921, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Information system monitoring and notifications using complex event processing

Complex Event Processing (CEP) is a novel approach how to process streaming events and extract information that would otherwise be lost. While tools for CEP are available right now, they are usually used only for a limited number of projects. That is disappointing, because every Enterprise Information System (EIS) is producing a high number of events, e.g. by logging debug information, and industry is not taking an advantage of CEP to make these information useful. We pick two concepts that seems to be from a different category -- notifications -- a ubiquitous way how to notify user of an EIS and EIS monitoring. With notifications we define a new abstraction upon notifications with respect to a separation of concerns to create a more maintainable implementation. In our research we show that this is a typical example of a possible future application of CEP and that the industry requires specific service oriented tools that can be used for both, notifications and monitoring. When these service oriented tools would be introduced into the industry it would promote EIS maintainability and extensibility.