A.14.4 MONITORAVGTHROUGHPUT

Monitors the average number of events flowing through the entry or exit point of a stage of the EPN of the specified application.

Syntax

java wlevs.Admin 
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ] 
    MONITORAVGTHROUGHPUT -application application 
    -stage stage -StagePoint stagePoint 
    -throughputInterval throughputInterval -avgInterval avgInterval
    -timeUnit timeUnit

Table A-34 MONITORAVGLATENCY Arguments

Argument	Definition
-application application	Specifies the name of the Oracle Stream Analytics application whose throughput and latency you want to monitor. To get the exact name of your application, you can: Use wlevs.Admin to query for the name (see Query for Application and Processor Names). Use the Oracle Stream Analytics Visualizer: Start the Oracle Stream Analytics Visualizer (see Using Visualizer for Oracle Stream Analytics). In the left pane, navigate to and expand the Applications node of the Oracle Stream Analytics instance to which the application is deployed. Each node under the Applications node is named with the exact application name. Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.
-stage stage	Specifies the name of the stage for which you want to monitor throughput of events. The stage is in the application specified by the -application option.
-stagePoint stagePoint	Specifies whether you want to monitor throughput at the entry- or exit- point of the specified stage. Valid values are entry and exit. Default value is entry.
-throughputInterval throughputInterval	Specifies the throughput interval across which throughput is calculated. Default value is 100. Specify the units with the -timeUnit option; default is milliseconds.
-avgInterval avgInterval	Specifies the average interval across which average throughput is calculated. Default value is 100. Specify the units with the -timeUnit option; default is milliseconds.

Example

The following example shows how to monitor the number of events flowing through the entry point of the cqlprocessor stage of the helloworld application:

java wlevs.Admin 
     -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector 
     -username wlevs -password wlevs 
     MONITORMAXLATENCY -application helloworld 
     -stage cqlprocessor -stagePoint entry 
     -throughputInterval 100 -avgInterval 100 -timeUnit MILLISECONDS