Webtrends Log Analyzer Advanced 8.x
Webtrends Log Analyzer 8.x
Webtrends Reporting Center 6.x
Webtrends Reporting Center 5.x
Webtrends Reporting Center 4.x
Last modified: 1/1/2011
Oftentimes it is difficult to determine the cause of a problem and various resulting error messages are key in determining the initial direction in which to troubleshoot. There are a couple of ways within Webtrends that will allow you to further these error messages to find a more meaningful indicator of the problem.
Why would a user want to increase the debug level?
An increased amount of data will be logged to the profile status. Often you will find more meaningful and detailed data about what is happening with the profile.
Why would a user not want to increase the debug level?
There are no performance issues resulting from this change. More space is, however, required to store the increased amount of data captured in the profile status log.
To change the debug level, follow the steps below:
1. Stop the reporting engine. For installations on Microsoft Windows NT or 2000, the user may do this from the Service panel. For Solaris and Linux this may be done from the command line by entering the following from the root of the Webtrends installation directory:
2. Access the wtm_wtx directory and locate the following file.
3. Locate the debuglevel value within the wtm_wtx.ini file. Increase the value as appropriate. The value may be increased to ten. Save the changes and close the file.
4. Restart the reporting server. For installations on Microsoft Windows NT or 2000, the user may do this from the Service panel. For Solaris and Linux this may be done from the command line by entering the following from the root of the
Webtrends installation directory.
Once the next analysis has been completed the user will notice a greater amount of detail provided within the profile status log.
To view this information for Webtrends 7.0 (steps vary in the later version), refer to KB article 051688.