Page Comparison

Table of Contents

Introduction

This sample demonstrates how to set up an execution plan with queries to detect suspicious login attempts to a user account. It generates an alert if it detects two or more login attempts are detected to the same user account from different IP addresses within a short time period. This sample uses wso2event for both inputs and outputs.

The query used in this sample is as follows:

    from every a1 = authStream
    -> b1 = authStream[username == a1.username and ipAddress != a1.ipAddress]
    within 10000
    select a1.username as username, a1.ipAddress as ip1, b1.ipAddress as ip2
    insert into alertStream;

In above query, we use patterns syntax

• Patterns syntax is used to identify two login attempts, received through the authStream, to the same account by two different

...

• IP addresses within 10 seconds

...

• . Such two events are named as a1 and b1.
• The arrow (->)

...

• denoted that b1 should occur after a1.
• The condition given inside

...

• brackets is

...

• used to capture events with the same user name

...

• but different

...

• IP addresses.
• The keyword 'within' specifies that this pattern should occur inside a 10,000 milliseconds time interval.

...

• Few attributes are selected and inserted to the alertStream.

...

• 'every' keyword ensures that CEP keeps searching for this pattern for every

...

• event received. If

...

• this keyword is omitted,

...

• CEP will search for the pattern only once, and any subsequent events will be discarded.

This sample uses wso2event for both inputs and outputs.

Prerequisites

For a list of prerequisites, please refer to the prerequisites section in Setting up CEP Samples.

...

Prerequisites

See Prerequisites in CEP Samples Setup page.

Building the sample

Start the WSO2 CEP server with the sample

...

configuration numbered 0104. For instructions, see Starting sample CEP configurations. This sample configuration does the following:

• Creates <CEP_HOME>/repository/conf

...

• /stream-manager-config.xml file, which is used to create the stream definitions

...

• for the sample.

...

• Points the default Axis2 repo

...

• to

...

• <CEP_HOME>/sample/artifacts/0104 (by default, the Axis2 repo is <CEP_HOME>/repository/deployment/server).

...

Executing the

...

sample

1. Open

   another terminal and switch

   a new terminal, go to <CEP_HOME>/samples/consumers/wso2-event and run ant from there.

   This will build the sample wso2event

   It builds the sample wso2event consumer and

   execute

   executes it.

   Info
   Do not close this terminal

   as it

   . It is required to keep the server running

   in order to receive events and view them

   and receiving events.

2. From

   Open another terminal

   switch

   , go to <CEP_HOME>/samples/producers/login-info

   /

   and

   run

   run ant

   from

    from there.

   This will build and run the

   
   
   It builds and runs the wso2event producer, which

   will send some

   sends sample login information to the CEP server.

   From

3. On this terminal,

   you will be able to view the details of the events sent.

   Once the step 3 is done successfully, you will be able to see see details of the output events (alerts on suspicious login attempts) received from the CEP via the terminal opened in step 2.

   Info
   title Note
   Since this sample uses random data and time-based patterns, different executions may result in produce different results. In some instances, if you limit the number of events sent to a very low number such as 3 or 4, you may not see a result at all.

   Below For example, given below is the console output of the consumer when sending 5 6 events from the producer.

   Image RemovedImage Added