Event Processor commands

You can use the following commands in the command-line interface to work with the event processor service:

Select NumEventsInQueue from Service where Name='EventProcessor';

Gets the number of events in the queue.

Select Events from Service where Name='EventProcessor';

Gets the events that are waiting to be processed.

Select ProcessingStatusHistory from Service where Name='EventProcessor';

Gets the processing status history.

Update Service set ClearQueue=true where Name='EventProcessor';

Clears the event queue. For all services except the PolicyLogger service you need to restart the service to implement the changes.

Select NumThreads from Service where Name='EventProcessor';

Gets the number of processing threads.

Select PoolConfig from Service where Name='EventProcessor';

Gets thread and connection pool information for diagnosis and makes recommendations.

The following example shows a thread analysis. In this example, the difference between the maximum and minimum processing threads is too large. To correct this issue, change the Min Processing Threads to 10. To ensure that the change is implemented, you must restart the EventProcessor service.

STARTRECORD
PoolConfig
-----------------------
---------------
THREAD ANALYSIS
---------------

Max Processing Threads: 15
Min Processing Threads: 2
Ratio of Max/Min Threads: 7.5

The following example shows a connection pool analysis example. The connection pool size for the SQL data sources that are listed in the example is smaller than the maximum number of threads in the EventProcessor service, which is 15. If you are concerned about performance, consider increasing the connection pool so that it is greater than 15. The increased connection pool size increases the workload for your database because it allows Netcool/Impact to make more connections to your database. You must ensure that the database can handle the increased workload without adversely affecting performance.

PASS:

defaultobjectserver

ACTION REQUIRED

DB2DS - Connection Pool size: 5

myflatfile - Connection Pool size: 5

MSSQLDS - Connection Pool size: 5

OracleDS - Connection Pool size: 5

EIC_alertsdb - Connection Pool size: 5

EventrulesDB - Connection Pool size: 2

SCR_DB - Connection Pool size: 5

ImpactDB - Connection Pool size: 5

ENDRECORD

READY

Select MinNumThreads from Service where Name='EventProcessor';

Gets the minimum number of processing threads.

Update Service set MinNumThreads = <minnumthreads> where Name='EventProcessor';

Sets the minimum number of processing threads. For example: Update Service set MinNumThreads = 10 where Name = 'EventProcessor';.

Update Service set MaxNumThreads =< maxnumthreads> where Name='EventProcessor';

Sets the maximum number of processing threads. For example: Update Service set MaxNumThreads = 50 where Name = 'EventProcessor';.

Select MaxNumThreads from Service where Name='EventProcessor';

Gets the maximum number of processing threads.

Update Service set MaximumThroughput = True where Name = 'EventProcessor';

Sets up the service to achieve maximum throughput.

Update Service set SaveTuningConfig = True where Name = 'EventProcessor';

Saves the tuned configuration for the next restart.

update Service set Running=false where Name='EventProcessor';

update Service set Running=true where Name='EventProcessor';

For more information about the Event Processor, see Event processor service in the online help. For more information about the command-line interface, see Using the command-line manager.