<< Click to Display Table of Contents >>

Navigation:  Automation Service Management > How to manage your environment with Management Console Web > Track >


If you have Traces set up on your project, all files generated as a result of them are accessible under this section.


The Tracing module has two tabs:





In this tab, you can see the traces generated in your projects. The visualization tab appears, as in the image below.




Here, five features are highlighted:

1. Filters: using the available filters, you can limit the list of the files displayed to make it easier to locate the file you want.

The following filters are available:

oCategory: select a category to find the trace file. The following categories are available:

Api: logs generated when an external interface or SAP BAPi is invoked

Connectors: logs generated when a Connector action is invoked.

Ecm: logs generated when Bizagi invokes the ECM service,

Execution: logs generated during the execution of Bizagi. This includes authentication, scheduler, and work portal.

Rpa: logs generated when a robot is executed.

Rules: logs generated the execution and evaluation of business rules and policies.

Uncategorized: let you find a file regardless of its category. This is the default value.

oDate range: select a range of dates when the trace file was created. The search is performed

oFile Name: provide the file name or its initial characters to located an specific trace file. The search is performed while you type.


2. Trace files: shows the list of trace files available in your environment, each files shows its name and creation date and they are sorted descending by the creation date, so the latest files appears first.


When you click any of the files displayed, a pop up windows appears with the content of the trace file. By default, most recent registers are displayed in this view, nevertheless, you can select a date to locate specific registers.




In the footer of the table, you can select the number of record per page displayed or navigate to other pages.


3. Download: once you select one or more trace files, this button becomes available to download the selected file. Alternatively, you can click the record and use the Download button.


4. Delete: once you select one or more trace files, this button becomes available to delete the selected Trace files.


5. Display density: allows you to modify the padding of the rows displayed in the trace files list. The following options are available.





In this tab, you can enable or disable the traces to be displayed in the Visualization option. Once you open this tab, you see the objects and components available:





The traces that you can configure through the Management Console Web are the same that can be configured in Bizagi Studio. For more information about these traces, refer to Tracing Configuration.


Defining the trace detail

To decide what alerts to trace, and what level of detail, navigate to the Tracing option you want and select the icon of its current detail level. Then, define the new detail level (None, Information, Warning, Error).




By default, Web_MC_058 None is selected and a minus sign appears for each trace object/component.

When Web_MC_059 Information is selected, the trace file logs warnings, errors and step-by-step information about the executed commands. This option traces all the log levels.

When Web_MC_060 Warning is selected, the trace file logs both warnings and errors.

When Web_MC_061 Error is selected, the trace file only logs errors.


You can select each trace type (and its subtypes) and select a trace detail configuration for each. If you select a parent level, all its children will have the same level, but you can change the level of any sublevel to set it independently.


If you want to set a trace detail for all types, you can use the Edit all traces option.