This article shows how to control the level of details that the Runtime will write into the log database, for each session.
The different log levels
Here are the different logLevel values and what level of details can be consulted, depending on the session status.
|logLevel||Running session||Successful session||Session with errors|
|-1||Not logged||Not logged||Not logged|
|0||Full details||Not logged||Full details|
|100||Full details||Session Header and Statistics||Full details|
|200||Full details||[logLevel 100] + Process Information and Statistics||Full details|
|300||Full details||[logLevel 200] + Actions Information and Statistics||Full details|
|400||Full details||Full details||Full details|
Example: at level 100, you can consult all details while the session is running. If it ends with errors, you can consult all session details. If it ends successfully, only the session's header and stats will be kept.
The level 100 is a great way to reduce the log database volume and keep track of execution times.
By default, processes are executed with the maximum log level (400).
Specifying the logLevel when developing the process
This will have effect on every session that has this process as a main process.
Specifying the logLevel on the command line
The syntax is as follows :
startdelivery.bat -name updateCustomers -logLevel 200
Specifying the logLevel when calling a webservice
When invoking a webservice exposed by Stambia, you can specify the logLevel in this way :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:stan="http://stambia.com/xsd/standard">
<stan:stambiaInput synchronous="true" sessionId="?" parentSessionId="?" logLevel="-1" sessionName="?"/>