General pointers and tuning tips

<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > System maintenance and monitoring > Monitoring > Bizagi Diagnostics >

General pointers and tuning tips

Overview

When monitoring and interpreting results in Bizagi Diagnostics, make sure you consider the following general pointers and tuning tips.

For introductory information about how to use Bizagi Diagnostics, refer to Using Bizagi Diagnostics.

 

General pointers

Consider the underlying concepts in Bizagi regarding how it optimizes its operations.

 

1. Application startup or restart presents different response times

When Automation Server starts up (or has been restarted from its Web server), it will load a significant amount of resources.

This means that the Apdex indicator may show a slower response time whenever Automation Server is initializing, and that this is normal behavior.

 

2. Recycling application resources

Based on the above premise, note that you may monitor and configure adequately how often resources are recycled by your Web server (e.g settings regarding pool cycling in the IIS), to achieve an optimal configuration where Automation Server resource recycling or restart does not significantly affect your operations.

 

Tuning tips

Consider the following tips and optimization parameters.

 

1. Allocated memory for Bizagi Diagnostics

For Automation Server projects which process a really large number of cases and activities on a daily basis (implying large volumes of information in logs), you may modify the memory allocated to Bizagi Diagnostics.

To do so, open the configuration file for the Diagnostics executable application which is located at C:\BizagiDiagnosticsTool\Bizagi.Diagnostics.Service\Bizagi.Diagnostics.Service.exe.config.

 

Modify the value for the ELK_Xmx (maximum) key which uses a default memory of 2147483648 bytes (2GB) according to your criteria and server characteristics.

 

Diagnostics_config3

 

2. Filter the events that are logged, or when to do so

In the Settings options in the Bizagi Diagnostics web application, you can define which Bizagi server events are recorded by logs, for all components of every Automation Server server.

Turn off those you do not identify as relevant for your needs, or define a threshold (in milliseconds) that limits when to record such events (to record only those exceeding the threshold duration):

 

Diagnostics_app_settings

 

After changing a setting, click Update.

Use the following table as a reference regarding the list of Bizagi server events.

 

BIZAGI SERVER EVENT

DESCRIPTION

Library rules execution

Applies to whenever Bizagi executes library rules (i.e, those which are frequently reused by being well-defined functions that receive inputs and outputs).

Web requests

Applies to requests that are solely web requests (HTTP).

Activate workitem

Applies whenever a new BPMN shape instance is made available by the logic behind the workflow.

BPMN shape instances include activities, Sub-Processes, events and gateways.

External service call

Applies to whenever Bizagi invokes an interface via the WS Connector.

Case processing (save and next)

Applies to requests that are solely produced when the user clicks Next or Save in an activity's user interface.

Jobs processing

Applies to whenever custom jobs run.

Custom traces

Applies to tracing features included by logic (i.e, scripting expressions using the CHelper.trace() method).

Business rules

Applies to whenever Bizagi executes rules (e.g, scripting expressions).

Build forms

Applies to whenever Bizagi loads user activities and displays their forms.

SQL Queries

Applies to running SQL queries as part of any request.

 

3. Define the best event recollection and storage system to employ

In addition for each Bizagi Work portal or Scheduler service you can define whether and how they record server events (e.g, which storage is used).

These options can be helpful according to how busy your system is, or which options you can consider best.

For instance, when using a File system, make sure the rate and filesize under which files are being created is appropriate for your environment.

To view all available options and to learn how to use additional possibilities, refer to Advanced options when recording server events.