

Programming Guides › Connector Programming Guide › Packaging and Deploying a Connector › Scripted Logic Update Considerations › Logging for Bundle Builder › Interpreting Log Messages
Interpreting Log Messages
Using the packaged logging configuration, the basic format of all log messages is:
- Date/Time - The timestamp on the local host when the message was logged. Format is ISO8601.
- The number of milliseconds elapsed from the construction of the layout until the creation of the logging event.
- Thread name - the name of the thread that handled the message e.g. [Timer-1]
- Bundle name - the name of the OSGi bundle that contained the executed code e.g. the text before the first ':' is the bundle name in (com.ca.jcs.core:com.ca.jcs.osgi.listener.ImplBundleServiceListener:123)
- Class name - the name of the class the log message originated from e.g. the text after the first ':' is the bundle name in (com.ca.jcs.core:com.ca.jcs.osgi.listener.ImplBundleServiceListener:123)
- Line number - when available, the line number in the class the log message originated from e.g. the text after the second ':' is the bundle name in (com.ca.jcs.core:com.ca.jcs.osgi.listener.ImplBundleServiceListener:123)
- Severity Level - The severity of the message e.g. INFO, WARN, ERROR
- Message - the log message supplied by the application
Copyright © 2013 CA.
All rights reserved.
 
|
|