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, four features are highlighted:
1. Filters: Using the Date from and Date to inputs, as well as the File name input, you can limit the list of the files displayed to make it easier to locate the file you want.
2. Select files: Select a set of files for deletion.
3. View: Click this button on a specific file, to display its online preview. This way you can quickly check a couple of records or get an idea of the information contained in the file.
4. Export: To download a Trace file for your own reference or analysis, click this button. The system prompts you to provide a file name and choose a location for the Trace file on your machine.
In this tab, you can enable or disable the traces to be displayed in the Visualization option.
Changes performed in this section will not be reflected in Bizagi Studio. All the changes performed in Bizagi Studio overrides this configuration.
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 to what level of detail, in the selected Tracing option, click the trace type and define its detail level (Error, Warning, All).
By default, None is selected and an empty box appears for each trace object/component.
When All is selected, the trace file logs warnings, errors and step-by-step information about the executed commands.
When Warning is selected, the trace file logs both warnings and errors.
When 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.