[ Bottom of Page | Previous Page | Next Page | Contents | Index ]

Profiling rules

Profiling generates a report that contains rule execution information. You can profile an entire rule base, rule sets, or particular rules. A report contains the following information for each rule being profiled:

• The amount of time (in seconds) spent by the rule to process the last event that triggered the rule
• The number of events processed by the rule
• The amount of time (in seconds) all events spent in the rule for processing
• The throughput of events for the rule, expressed as the number of events per second

The following figure shows an example of a profile report with one rule profiled:

============================================
              Timing Summary
--------------------------------------------
test_rls:
  Time for last Event: 7.000000000000001e-02
  Event Count:         2
  Total Time:          4.799999999999998e-01
  Events per second:   4.166666666666669e+00
--------------------------------------------
--------------------------------------------
============================================

To profile rules, you must compile the rule base with profiling enabled. This can be done from the command line with the wrb -comprules -profile command or with the profile directive specified in a rule set or rule.

After recompiling the rule base with profiling enabled, stop and restart the event server to begin the profiling. The profile report is appended to the $DBDIR/tec/profile file when you shut down the event server. Because a profile report is always appended to the same file it can become quite large if you never delete it or delete entries within it, so check it periodically.

[ Top of Page | Previous Page | Next Page | Contents | Index ]