| Administering Indications and Instances Using HP SMH | ||
|
| Tracing EVWEB | |
Table |
| Entries in sfm.log (Continued) | |
|
|
|
|
Field |
| Description |
|
|
|
|
|
Module Name |
| Displays the name of the |
|
|
| module or the providers that |
|
|
| logged the message in the |
|
|
| sfm.log file, for example, |
|
|
| EVWEB_CLI, FMDProviders. |
|
|
|
|
|
Severity |
| Displays the severity of the |
|
|
| message logged in the |
|
|
| sfm.log file. |
|
|
|
|
|
Process ID |
| Displays the |
|
|
| ID. |
|
|
|
|
|
Thread ID |
| Displays the thread ID. |
|
|
|
|
|
Message |
| Displays the text message. |
|
|
|
|
|
To change the default location of the sfm.log file, you must configure the /opt/sfm/conf/fmloggerconfig.xml file.
You can enable tracing for an EVWEB session. A session is the duration between a login and a logout. When you enable tracing, make sure that you set a trace level. EVWEB logs traces for a session for the set trace level. At the end of a session, tracing is automatically disabled. In an active session, the trace level remains valid until you modify it.
The traces for a session are also logged in the samlog.log. The path to the samlog.log file is /var/sam/log/samlog.log. From the GUI, you can access the samlog.log file from HP SMH home page
NOTE | Tracing is available for administrators only. However, |
| |
|
|
Chapter 4 | 101 |