ࡱ> EGD7 bjbjUU *(7|7| l88 D4q98888888$; 1=l99+988>n4@7x #zj 45 7 A90q95==7Logging The CIMOM infrastructure components will use the Logging Interface to log messages. Messages will be logged to a standard CIM log file. The location of the log file can be specified using the Configuration framework. Log Levels Log messages have an associated Log Level. The Level gives a rough indication about the importance of a log message. The following are the log levels. CRITICALCritical conditions, such as hard errorsERRORErrorsWARNINGWarning messagesNOTICEConditions that are not error conditions, but should possibly be handled speciallyINFOInformational messages Logging levels can be activated using the Configuration framework. The Log levels CRITICAL, ERROR and WARNING will be enabled by default. Configuration Properties for Logging LOG_LEVEL [ CRITICAL|ERROR|WARNING|NOTICE | INFO ] LOG_FILE_MAX_SIZE [ in KB ] LOG_FILE_LOCATION General Format for Log Messages Timestamp Log Level Detailed Description Log Message ID Log Interface log ( int logLevel, int logMsgID, char* formatString, ) Tracing The CIMOM infrastructure components will use the Tracing Interface to provide trace messages that will be helpful in investigating a problem cause. Tracing can be enabled on a per component basis, E.g. Repository, Configuration framework, Query processor etc. Trace Levels Trace messages can be associated with the following levels. Level 0Error/Exception trace messagesLevel 1Warning trace messagesLevel 2Basic logic flow trace messages (Function Entry/Exit) and minimal data detailLevel 3Intra function logic flow and moderate data detailLevel 4High data detail Tracing for components and levels can be activated using the Configuration framework. Configuration Properties for Tracing TRACE=[ON/OFF] TRACE_COMPONENT=Components TRACE_LEVEL=[0|1|2|3|4] TRACE_FILE General Format for Trace Messages Timestamp Component Level Process Name PID Thread ID Detailed Information Trace Interface trace ( int traceComponent, int traceLevel, char* formatString,) Issues How will the CLIs (E.g. WbemExec), Client API, IPC Providers perform Tracing and Logging? Will they log to the same file as CIMOM? Will they log to different files? If they log to the same file, how will the Write operations be synchronized? How to control IPC Provider Tracing? How to correlate CIMOM and Provider trace messages? Will MSGID be useful for this purpose? Will Class name and Method name be part of the Trace Messages? Logging and Tracing Infrastructure Specification Roger Kumpf (roger_kumpf@hp.com) Hewlett-Packard Company Page  PAGE 1 Z[lm  o p   B C \ ]  & ' 46lmstuv0JCJmHnHu0JCJj0JCJUCJCJ;CJ;6] CJOJQJCJ8 ]^<8hlD$$Ifl0T,"T64 lal$If <=BYZ[ >Zlmt & F  & F $IfD$$Ifl0T,"T64 lal  + g h p   \D$$Ifl0 64 la$If  B C K \ ] ^   & ' I S ] c p h & F & F D$$Ifl0 64 la$Ifp t ~ e f 456 ! & F ! (&P1h/R / =!"#$% i8@8 NormalCJ_HaJmH sH tH R@R Heading 1$$@&a$5B*CJOJQJ\^Jph2@2 Heading 2$@&5\N@N Heading 3$<@&5CJOJQJ\^JaJ>@> Heading 4$@&5CJOJQJ\<A@< Default Paragraph FontFB@F Body Text$a$B*CJOJQJ^Jph, @, Footer  !,@, Header  !&)@!& Page Number0P`20 Body Text 26]               ( ]^<=BYZ[ >Zlm+ghpBCK\]^&'IS]cpt~ e f 4 5 6 (0000080(000000000000000000000(0 0 0 00(0 0m 0m 0m 0m0m(000(000000(00000000000000000000(0 0 0 0 00(0 0' 0' 0' 0' 0' 0' 0'0'(000(00000000000@0@0@0@0@0 0000000000000000 < p  !D"@!0(  B S  ? 6 7 g w w x x  l v E-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-ClientE:\Tracing\latest\T&L Spec.docE-Client#E:\Tracing\latest\Specification.docE-Client%C:\wbem\Tracing\T&L Specification.doc h),# |mt<>9b"X(<, o',R^ndQRNJXlZrXx^r**dZdbjOlZ_ hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( ^`OJQJo( ^`OJQJo(o   ^ `OJQJo(   ^ `OJQJo( xx^x`OJQJo(o HH^H`OJQJo( ^`OJQJo( ^`OJQJo(o ^`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( ^`OJQJo( ^`OJQJo(o   ^ `OJQJo(   ^ `OJQJo( xx^x`OJQJo(o HH^H`OJQJo( ^`OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o   ^ `OJQJo(   ^ `OJQJo( xx^x`OJQJo(o HH^H`OJQJo( ^`OJQJo( ^`OJQJo(o ^`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo(h^`.h ^`OJQJo(hpLp^p`L.h@ @ ^@ `.h^`.hL^`L.h^`.h^`.hPLP^P`L. hh^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( "^dZdrX|mQR<><,# NJXjOlh)', 4        4        4        4        4        4        4        4        4        4        4         4       4        <=BYZhpBCK\] @  T," @UnknownGz Times New Roman5Symbol3& z Arial7&  Verdana5& z!Tahoma?5 z Courier New;Wingdings"1hglVfglVf_lVfeY0d  @QTracing & LoggingE-ClientE-ClientOh+'0 ( D P \ ht|Tracing & Loggingdrac E-Client Lo-Cl-Cl Normal.doto E-Clientto2ClMicrosoft Word 9.0@G@:Ii@jgj@jgje՜.+,0 hp  Hewlett-Packard  Tracing & Logging Title  !"#$%&'()*+,-./012356789:;=>?@ABCFRoot Entry FzjH1Table=WordDocument*(SummaryInformation(4DocumentSummaryInformation8<CompObjjObjectPoolzjzj  FMicrosoft Word Document MSWordDocWord.Document.89q