The Logs and Traces plug-in in the SAP NetWeaver Administrator allows you to view all list and text formatted logs and traces that are generated from the J2EE engine. You can access the Logs and Traces plug-in by choosing System Management -> Monitoring -> Logs and Traces.
You can configure logs and traces in the Log Configuration plug-in in the SAP NetWeaver
Administrator. An important part of any log and trace message is its severity. This denotes the level of importance or relevance of a certain message. Log and traces can be limited to certain severity levels, that is, only data of a defined severity is collected. The order of the constants is, with increasing severity:
1. DEBUG – For debugging purpose, with extensive and low level information
2. PATH – For tracing the execution flow, for example, used in the context of entering and leaving a method, looping and branching operations
3. INFO – Informational text, mostly for echoing what has already been performed
4. WARNING – The application can recover from an anomaly and fulfill the required task, but needs attention from a developer/operator
5. ERROR – The application can recover from an error, but it cannot fulfill the required task due to the error
6. FATAL – The application cannot recover from an error, and the severe situation causes fatal termination
Categories and locations are associated with a severity. This acts as a filter where only those messages that are of equal or higher severity can pass.
Unless you are performing troubleshooting you should set severities to ERROR. Otherwise considerable system resources are used to write large amounts of logs and traces. For more information check the Technical Operations Manual for SAP NetWeaver
No comments:
Post a Comment