Events User Manual: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 15: Line 15:
Record interaction with a load generator. This example was based on NeoLoad.
Record interaction with a load generator. This example was based on NeoLoad.


Mark the target business scenarios.
Mark the start of the target business scenarios.


Design -> Virtual User Profiles -> Style Reader -> Actions -> Style - Seasons - Style - Style Sample - Style Gallery -> First Page -> First Request in the page -> Advanced -> Request headers.
Design -> Virtual User Profiles -> Style Reader -> Actions -> Style - Seasons - Style - Style Sample - Style Gallery -> First Page -> First request in the page -> Advanced -> Request headers:


Add a new header: "Business-Scenario-Start-Marker" (the value is available in [https://github.com/NovaOrdis/esa/blob/master/src/main/java/io/novaordis/esa/extensions/bscenarios/BusinessScenario.java BusinessScenario.java])
Add a new header: "Business-Scenario-Start-Marker" (the exact name is available in [https://github.com/NovaOrdis/esa/blob/master/src/main/java/io/novaordis/esa/extensions/bscenarios/BusinessScenario.java BusinessScenario.java]). The value of the header should be business scenario type.


Mark the end of the target business scenarios.
Design -> Virtual User Profiles -> Style Reader -> Actions -> Style - Seasons - Style - Style Sample - Style Gallery -> RequestHandler_16 -> First request in page -> Advanced -> Request headers:
Add a new header: "Business-Scenario-Start-Marker" (the exact name is available in [https://github.com/NovaOrdis/esa/blob/master/src/main/java/io/novaordis/esa/extensions/bscenarios/BusinessScenario.java BusinessScenario.java]). Empty value.


==Prepare the Target Environment==
==Prepare the Target Environment==

Revision as of 06:22, 22 April 2016

Internal

Overview

A HttpEvent contains all the query parameters under a “query” MapProperty.

A HttpEvent contains all the incoming headers under a “incoming-headers” MapProperty.

Business Scenario Measurement Procedure

Record the Load Scenarios

Record interaction with a load generator. This example was based on NeoLoad.

Mark the start of the target business scenarios.

Design -> Virtual User Profiles -> Style Reader -> Actions -> Style - Seasons - Style - Style Sample - Style Gallery -> First Page -> First request in the page -> Advanced -> Request headers:

Add a new header: "Business-Scenario-Start-Marker" (the exact name is available in BusinessScenario.java). The value of the header should be business scenario type.

Mark the end of the target business scenarios.

Design -> Virtual User Profiles -> Style Reader -> Actions -> Style - Seasons - Style - Style Sample - Style Gallery -> RequestHandler_16 -> First request in page -> Advanced -> Request headers:

Add a new header: "Business-Scenario-Start-Marker" (the exact name is available in BusinessScenario.java). Empty value.

Prepare the Target Environment

On the target environment, reset the application server node:

cd /c/ovidiu/bin
./environment.sh stop
./environment.sh start

The start script will also clean the previous logs.

Run the Test

Shut Down and Collect Data

cd /c/ovidiu
./bin/environment.sh stop

All log data is collected and zipped under /c/ovidiu/data/load-data-yy-mm-dd-hh-mm-ss...zip

Download the test data locally via the QLB-APP02-Redirected-Folder on NOMBP2.

Unzip it in its own separated directory.

The data export script keeps the access log as “access_log.log” and places the definition of the access log fields in access_log.def.

Data Processing

Do initial parsing:

esa < ./access_log.log --input-format-file=./access_log.def 

esa < ./access_log.log --input-format-file=./access_log.def  describe

Extract per-scenario statistics:

esa < ./access_log.log --input-format-file=./access_log.def perf > business-scenarios.csv

Scatter plot the results.