Share via

MOM Logging Part 2

  • Article

 

Sorry for the delay...

 

Before we look at specific MOM logs and what information they contain, let's talk about the types of logging available.

 

In part 1, we talked about the .mc8 logs and the registry keys that are used to tweak logging.  There are a couple of other registry keys that we need to talk about.

 

Das Logging (Database Access Services) - this logging (under dllhost*.mc8 log files), records the DAS activity - data into the Onepoint database.

 

Its set using the following key:

 

HKLM \ Software \ Mission Critical Software \ DASServer \ LoggingFlags set to ffff. (0 is disabled)

 

Tracelevel (covered in Part 1) must be set to 9 for Das Logging to be enabled.

 

To activate it, you have to restart the MOM Das Com+ Application.  These logs are written to the profile of the DAS account, under Local Settings \ Temp \ Microsoft Operations Manager. 

 

The Das log is useful for troubleshooting SQL type errors, or data stream type issues, like seeing the performance counter data that is being inserted into Onepoint.

 

 

Das logging should not be enabled unless you are troubleshooting a database related issue - keeping Das Logging enabled can cause performance degradation in writing to the Onepoint database.

 

 

A second type of logging is dbconnector logging.  Dbconnector logging is described in 901049:

 

 

https://support.microsoft.com/?kbid=901049

 

 

Basically, enabling this will cause all data items (events, performance data, alerts, and discovery data) that are inserted into the Onepoint database, to also be written to dbconnector.xml, under %windir% \Temp\Microsoft Operations Manager.

 

This file will grow very large very quickly, so do not leave this logging enabled unless you are trying to capture specific data from your agents.

 

 

Finally, DebugView from Sysinternals is a great utility for getting additional logging from MOM, especially during setup (in addition to the verbose MSI logs), and the MMPC (MOM to MOM Product Connector) execution.  In fact, DebugView provides verbose DAS type logging for the MMPC, normal DAS logging does not capture any additional MMPC database activity.

 

In the 3rd part (which will be out much sooner that part 2), we will go through the other MOM 2005 logs and what they are used for.