Page tree
Skip to end of metadata
Go to start of metadata

The Performance Logger is a useful debugging tool for logging the job's performance statistics which are generated when you activate the Performance Reports. It writes jobs to a log file (if a log file is specified), generates an average of execution paths detected and also captures the last "numJobs" jobs in memory to be displayed on the admin interface. This component an extension of Job Logger.

The job is logged after it has completed its execution, this stage register itself as a job listener. This is done to log all the performance reports generated in all subsequent stages after this one.

To enable/disable this feature visit Performance Reports.

WARNING: This job logger creates all the directories required to create the logFile. Naturally, this makes it easier to use, but it does mean you need to be careful about where the log file is stored.

Where to use this component

This is an Aspire Stage, so it must be added to the execution path of the jobs in interest. Anywhere in that execution path would work, but we recommend using it as the first stage executed for consistency among all applications.

Performance Logger
Factory Namecom.searchtechnologies.aspire:aspire-tools


InputsThe entire jo.
OutputsThe input job's performance statistics are sent, unmodified, to the output, after loggin.


logFileStringnull(Optional) Specifies the file name to which jobs are logged. If missing, then no log file will be created. Note that directories required for the log file will be automatically created.

Automatically creates the directories necessary to contain the log file if they don't already exist.

If the log file already exists, first it checks for a ".bak" version of the file. If that exists it is deleted. Then it renames the current file to ".bak", and creates the new file.

enablebooleantrueIf true, enables logging and average time calculations.
numJobsint5Specifies how many of the most recent jobs will be displayed from the admin interface. Set this number to zero if you don't want to keep any files in memory (i.e. just write to the log file), which you may prefer to do if your documents are very large and therefore may use up a lot of memory.

Example Configuration


<component name="PerformanceLogger" subType="performanceLogger" factoryName="aspire-tools">


<component name="PerformanceLogger" subType="performanceLogger" factoryName="aspire-tools">

Example Output



Downloading of Performance Reports

To download the reports generated by this component you need to go to the component's debug console page.

Once in the debug console page you can select the format of your choice to download the report, and then click on the button named "downloadExecutionPaths".

Performance logger debug.png

An execution path is the ordered list of applications, pipelines, stages and workflow rules in which each document was processed. There can be different execution paths for documents scanned from the same connector, this is because there can be different processing rules for different types of documents (such as Folders/Files). You can also create new execution paths by adding some flow control rules to your workflow.

Example Output

In CSV format:


In XML format:

<executionPath averageTime="10927" count="1">
  <pipelineManager averageTime="10926" name="/FeedOneExample/StandardPipeManager">
    <pipeline averageTime="10926" name="doc-process">
      <stage averageTime="0" name="/FeedOneExample/StandardPipeManager/PerformanceLogger"/>
      <stage averageTime="5595" name="/FeedOneExample/StandardPipeManager/FetchUrl"/>
      <stage averageTime="5330" name="/FeedOneExample/StandardPipeManager/ExtractText"/>
      <stage averageTime="0" name="/FeedOneExample/StandardPipeManager/ExtractDomain"/>
      <stage averageTime="0" name="/FeedOneExample/StandardPipeManager/PrintToFile"/>
  • No labels