Steps to reproduce:
https://www.zabbix.com/documentation/8.0/en/manual/events/complex_event_processing

The current Zabbix event processing documentation focuses primarily on component-level interface semantics rather than foundational execution models. While it exhaustively catalogues user-facing configuration fields and button toggles, it lacks architectural clarity on state evaluation ordering, event correlation lifecycles, and real-world processing patterns, requiring empirical trial-and-error to understand actual system behavior.

Result:

• no basics information with diagrams like what is sliding window, how it works
• no infomation of is possible, all features which can be configured
• no real life examples of the features supported
• no performance description
• no example how to build topology for root cause analysis
• no easily available information what JS code can be used within CEP

From the user’s perspective, it looks as "Complex" as it named CEP.

Expected:

• Implemented engine logic described with diagrams and specs
• Usage example covered for all possible cases