WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.
Skip to end of metadata
Go to start of metadata


This sample demonstrates how to set up an execution plan with a filter query that checks for some specific conditions and then outputs a custom alert event when the conditions are true. Custom events are events with custom mappings that does not adhere to the default event formats. For more information on event formats, see Event FormatsThis sample uses the Event Simulator for inputs and the logger publisher for logging the outputs to the CEP console.

The execution plan used in this sample is as follows:

from TempStream [ roomNo > 245 and roomNo <= 365 and temp > 40 ]
select roomNo, temp
insert into AlertServerRoomTempStream ;

The first query,

  • Processes the events received through the TempStream
  • Inside the filter, checks for the condition roomNo > 245 and roomNo <= 365 and temp > 40
  • If the condition is true, 
    • Selects the attributes (roomNo, temp) specified under the select clause, from each event received.
    • Emits those events as output events through the AlertServerRoomTempStream stream.


Set up the prerequisites required for all samples.

Building the sample

Start the WSO2 CEP server with the sample configuration numbered 0103. For instructions, see Starting sample CEP configurations. This sample configuration does the following:

  • Points the default Axis2 repo to <CEP_HOME>/samples/cep/artifacts/0103 (by default, the Axis2 repo is <CEP_HOME>/repository/deployment/server).

Executing the sample

  1. Log into the CEP management console which is located at https://localhost:9443/carbon.

  2. Go to Tools -> Event Simulator. Under the 'Multiple Events' section, you can see the listed 'events.csv' file which contains some sample data. Click Play to start sending sample events from the file.
  3. See the output events received from the CEP console. This sample uses the logger adaptor to log output events to the console.

    For example, given below is a screenshot of the output of the consumer sending events from the producer:

  • No labels