This documentation is for WSO2 Complex Event Processor 4.0.0. View documentation for the latest release.
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

The Siddhi Try It is a tool used for experimenting event sequences through Siddhi Query Language (SiddhiQL) statements. You can define an execution plan to store the event processing logic and input an event stream to test the Siddhi query processing functionality.

Follow the steps below to use the Siddhi Try It tool.

  1. Log in to the CEP management console, click Tools, and then click Siddhi Try It as shown below.
    Tools menu
  2. Enter the Execution Plan as shown in the below example. 
    sample execution planThe main elements of an execution plan are described below.

    For more information on execution plans, see Working with Execution Plans.

    ElementDescriptionExample
    Execution plan nameThe name of the execution plan. It can contain only alphanumeric characters and '_' character.TestExecutionPlan
    Input streamThe mappings between the available event stream and the input stream of the Siddhi runtime, which is defined inside the query expressions.sensorStream
    Query expressions

    The event processing logic written in Siddhi QL.

    When defining more than one query, end each query with a semicolon. Defining a query name (e.g. query1) is optional.

    @info(name = 'query1') 

    from sensorStream[temperature>98.6] 

    select sensorId

    insert into outputStream;

    Output streamThe mappings between the output stream of the Siddhi runtime and one of the available event streams, which is defined inside the query expressions.outputStream
  3. Enter a time stamp to begin the process of sending events for Begin Time if required.

  4. Enter the Event Stream, which is a logical series of events ordered based on the time as shown in the below example. 

    An event stream can contain a delay between events. When defining a delay, enter the delay time in milliseconds as shown in the example below. Furthermore, for scheduler related queries, you need to set up a delay with a necessary time in the event stream. For more information on event streams, see Working with Event Streams.

    sample input event stream

  5. Click Submit.
    You view the input stream and the results of the execution plan under the defined output stream, and separated query outputs as shown below.
    output of the execution plan
  • No labels