MicroStrategy ONE

How to Determine What and Where Information is Logged

Tasks performed by MicroStrategy Web users may generate errors, warnings, or messages in MicroStrategy Web. This information can be stored in log files. Logs are records of all low-level activity, which can be aggregated and used for troubleshooting a specific problem or for server and system analysis. You can define what information is logged by MicroStrategy Web and where it is logged.

  1. Access the MicroStrategy Web Administrator page. (How?)

  2. From the pane on the left, select Configuration. The Diagnostics Configuration page opens.

  3. Select either Internal diagnostic setup or Custom diagnostic setup to determine the type of log to create.

    • Internal diagnostic setup: This is the default option and is used to set the type of information to be logged in the log file. The settings defined here are written in the logger.properties file.

      • Level: Select the level at which the information is written in the log file. You can choose from the following levels:

        • OFF: Nothing is written in the log file.

        • Errors: This is the default option. Errors generated by MicroStrategy Web are included in the log file.

        • Warnings: Errors and warnings generated by MicroStrategy Web are included in the log file.

        • Messages: Errors, warnings, and messages generated by MicroStrategy Web are included in the log file.

      • Log files directory: This field displays a default path where the log files are saved. You can also specify a different path. The log file is generated in the specified path in the MSTRmmddyyyy.log_num format.

        The naming of the log file is handled by the logger.properties file. For example, the first log file created on 01/02/2008 appears asMSTR01022008.log_1.

      • Maximum output file size: The maximum size, in bytes, of the log file. When the maximum file size is reached, a new log file is started.

      • Number of file outputs: The maximum number of log files that Web creates.

        Logs can also be created to better identify and debug API issues. These logs are configured in the Advanced Logger Settings area. For details and steps, see Creating logs to debug API issues.

    • Custom diagnostic setup: This option is typically used to load a logger.properties file provided to you by MicroStrategy Technical Support.Thelogger.properties file contains the internal diagnostics setup settings above, and is saved by default in the CATALINA_HOME\webapps\MicroStrategy\WEB-INF\log folder. You can load diagnostics settings contained in the file, get the output, and send it back to Technical Support. When the Technical Support engineer is done, they can reset your log to its original settings. This allows for a very detailed level of logging without you having to write the logger.propertiesfile yourself.

      • Specify the path to the logger.properties file in the Path to custom diagnostics setup file field.

  4. Click Save.

  5. From the pane on the left, select Security. The Security page opens.

  6. Determine if exception information and/or request information in the page's source is included in the logs by selecting or clearing the Include exception information in the page source and Include request information in the page source checkboxes.

  7. Click Save.

Related Topics

How to View Logs

View Logs Page

How to Enable and View Statistics