In some instances, we require as much detail in logging as humanly possible to help troubleshoot an issue.  To this end, we utilize debug level logging.

In Operations Manager SP1, this feature is installed by default.  It is situated in the OpsMgr program folder under tools.

To start the verbose logging, stop the health service on the OpsMgr system and issue the command starttracing.cmd VER .  Then start the health service again.

The log files themselves are stored in the %windir%\Temp\OpsMgrTrace folder.  They will be in .etl format which are not directly readable.  From there, we issue the command: formattracing.cmd.  This will format the log files so that they are readable.

For console issues, the UI log would be of interest whereas for agent issues look to the agent log.

In the OpsMgr_install_folder\Tools directory there is a txt file with the logfile name which contains details about what gets logged to each.

Read the complete post at http://owsug.ca/blogs/brad/archive/2008/09/03/Event-Tracing-for-Windows-or-ETL-logging-for-OpsMgr.aspx