Hi Seshika, Adding a delay is already possible in the simulator. Thank you for the suggestions. We will surely look into those as well.
Best Regards, On Thu, Sep 3, 2015 at 5:35 PM, Seshika Fernando <[email protected]> wrote: > Hi Ramindu, > > The existing event simulator feature is extremely useful. IMO what would > add to its usability is the following... > 1. ability to provide a delay between events > 2. ability for user to specify how many events to be sent (currently all > events in the file will be sent) > 3. ability to pause and play the simulation. > > Maybe you can consider the above, for future improvements. > > seshi > > On Wed, Sep 2, 2015 at 7:53 PM, Ramindu De Silva <[email protected]> > wrote: > >> Hi all, >> >> Please find the image in the attachment below. Sorry for the >> inconvenience caused. >> >> Best Regards, >> >> On Wed, Sep 2, 2015 at 7:43 PM, Ramindu De Silva <[email protected]> >> wrote: >> >>> Hi all, >>> >>> Event simulator feature is a component already available in the CEP >>> which enables the user to simulate an event flow. The events will be flown >>> through, starting from the selected event stream. These events will be >>> created within the CEP without using any event receivers. Following diagram >>> illustrates the high level architecture. >>> >>> There are three options to simulate an event flow >>> >>> 1. Entering attribute values and simulating one event >>> In this scenario, one event will simulate using the values >>> entered, using a form which enables the user to fill in the value next to >>> the event stream attribute. >>> >>> 2. Using a csv file containing several events data >>> In this scenario, several events can be simulated using an >>> uploaded csv file. The csv file contains the attribute values in the order >>> of the event stream separated by an user defined character. >>> >>> 3. Using a rdbms table data and simulating several events >>> In this scenario, the user will specify a rdbms data source, a >>> table and column names with stream attributes to simulate its data. >>> >>> The implementation can be found in the repository [1] >>> >>> Do share your suggestions and thoughts on the $subject. >>> >>> 1. >>> https://github.com/wso2/carbon-event-processing/tree/master/components/event-simulator >>> >>> Best Regards, >>> >>> -- >>> *Ramindu De Silva* >>> Software Engineer >>> WSO2 Inc.: http://wso2.com >>> lean.enterprise.middleware >>> >>> email: [email protected] <[email protected]> >>> mob: +94 772339350 >>> mob: +94 782731766 >>> >> >> >> >> -- >> *Ramindu De Silva* >> Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> email: [email protected] <[email protected]> >> mob: +94 772339350 >> mob: +94 782731766 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Ramindu De Silva* Software Engineer WSO2 Inc.: http://wso2.com lean.enterprise.middleware email: [email protected] <[email protected]> mob: +94 772339350 mob: +94 782731766
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
