For the last couple of weeks, I started to work with Microsoft BHOLD suite. If you’re new to the product, you’ll soon find out that the logging of the BFSS and BFPC services is a good starting point in trying to solve issues. Here’s some information on the logging configuration of these services.
By default, all information is logged to the files ‘BFSS.log’ and ‘BFPC.log’ in the ‘C:\temp\’ folder. To change the directory in which these files are stored, create a registry key in ‘HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\b1Core\LogfileDir‘, containing the directory (without the filename) where you want the logfiles to be stored.
You can also add the ‘BFSSLogLevel’ and ‘BFPCLogLevel’ keys. This suggests that it is possible to control the amount of messages logged, but it doesn’t. If the value is set to ‘verbose’, all available information is logged. Any other value (like ‘none’ or ‘warning’ / ‘error’) stops all logging for the BFSS and limits the logging for BFPC to things like ‘BFPC Initialising’ and ‘BFPC Ended’.
To summarize: there aren’t much possibilities to configure logging, it’s basically all or nothing. The information above could prove value in changing the default log location and disabling logging in your production environment. This is most recommended because if verbose logging is enabled (which it is by default), this will result in gigabytes of logdata per day!