Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Use the V4.2 Profiler tool to monitor performance of an activity

Updated on November 15, 2015


A developer asks:

We would like to leverage the Performance tool to get more details down at the activity level.

When an MQ feed comes into the system, we would like to identify which activities and which steps took more time and need enhancements.

From the beginning to the end, about 60 activities execute.Is there a way to get this detail at a higher level -- rather than instrumenting all 60 activities?

Suggested Approach

The Performance tool (PAL) doesn't help in this case because it does not report performance down to the activity level. PAL displays tell you only the elapsed time of services.. 

Version 4.2 includes the Profiler tool , which writes to a logfile the timestamps for activities and a few other rule type s as they are executing. 

Operation of the Profiler tool is controlled by settings in the pegarules.xml file.  You can't restrict the Profiler to record only service activitiess only, but in a controlled test environment you could gain useful information.

For instructions on the V4.2 Profiler, see the System Tools paper Using Performance Tools 4.2.


  • Previous topic Overview of the Performance Tools (PAL)
  • Next topic Using the DBTrace and Profiler tools to understand performance

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us