I made a research to determine how the management of the
traces functions.
Configuration :
Windows XP Pro SP2
OpenSTA 1.4.2.34
Local Test Execution
Here my observations:
Trace levels :
0 : None
10 : Low
20 : Medium
50 : High
The file "Repository/TraceSettings.txt" is only created when
you validate (with button Ok) the "Trace Settings" values in
Commander, "Menu Tools->Trace Settings"
(BaseUI/Commander/TraceSetDlg.cpp, function OnOK() ).
This file contains the trace level for 5 categories : HTTP,
SNMP, NT Performance, Test Manager and General. It is copied
in the directory "OpenSTA/Engines/Temp" on each injector
host before the test execution
(Architecture/CyrDaemon/CyrVDK010/RemoteRepository.cpp,
function CheckoutTraceSettingsFile() ).
The trace level is used to set the command line option "-v"
to run the test executer, TExecuter_htp.exe for example,
(Architecture/CyrDaemon/CyrVDK010/InjectorControl_i.cpp,
function StartTaskGroup() ).
When this file doesn't exist, the trace level is defined to
10 for the 5 categories
(Architecture/CyrDaemon/CyrVDK010/RemoteRepository.cpp,
function GetTraceLevel() ).
The level used to create the HTTP Executer log file
("TExecuter_htp_@IP.log") is the maximum between the value
of the "-v" option and the value of the field "TraceLevel"
(or 0 if inexistent) in the file
"Engines/TestExecuter_web.ini"
(HTTP/Executers/ThreadPoolSources/TEMainStructure.cpp,
function CommonInit() ).
For this file, the difference is apparently very little
between levels 0 and 10.
When the HTTP Executer is used by the Modeler
(TEHttpLib.dll), the log file is
"Engines/Web/Modeller/TModeler_Web.log" and the trace level
is always 50
(HTTP/Executers/ThreadPoolSources/TEMainStructure.cpp,
function CommonInit() ).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=949869
I made a research to determine how the management of the
traces functions.
Configuration :
Windows XP Pro SP2
OpenSTA 1.4.2.34
Local Test Execution
Here my observations:
Trace levels :
0 : None
10 : Low
20 : Medium
50 : High
The file "Repository/TraceSettings.txt" is only created when
you validate (with button Ok) the "Trace Settings" values in
Commander, "Menu Tools->Trace Settings"
(BaseUI/Commander/TraceSetDlg.cpp, function OnOK() ).
This file contains the trace level for 5 categories : HTTP,
SNMP, NT Performance, Test Manager and General. It is copied
in the directory "OpenSTA/Engines/Temp" on each injector
host before the test execution
(Architecture/CyrDaemon/CyrVDK010/RemoteRepository.cpp,
function CheckoutTraceSettingsFile() ).
The trace level is used to set the command line option "-v"
to run the test executer, TExecuter_htp.exe for example,
(Architecture/CyrDaemon/CyrVDK010/InjectorControl_i.cpp,
function StartTaskGroup() ).
When this file doesn't exist, the trace level is defined to
10 for the 5 categories
(Architecture/CyrDaemon/CyrVDK010/RemoteRepository.cpp,
function GetTraceLevel() ).
The level used to create the HTTP Executer log file
("TExecuter_htp_@IP.log") is the maximum between the value
of the "-v" option and the value of the field "TraceLevel"
(or 0 if inexistent) in the file
"Engines/TestExecuter_web.ini"
(HTTP/Executers/ThreadPoolSources/TEMainStructure.cpp,
function CommonInit() ).
For this file, the difference is apparently very little
between levels 0 and 10.
When the HTTP Executer is used by the Modeler
(TEHttpLib.dll), the log file is
"Engines/Web/Modeller/TModeler_Web.log" and the trace level
is always 50
(HTTP/Executers/ThreadPoolSources/TEMainStructure.cpp,
function CommonInit() ).