Overview of the MicroStrategy Diagnostics and Performance Logging tool

In some cases, there is not enough existing functionality to troubleshoot the issue. In this case we should use the MicroStrategy Diagnostics and Performance Logging (DAPL) tool. It allows us to enable trace. Let's open the DAPL tool using the CLI:

# cd /mstr10/microstrategy_home/HealthCenterInstance/bin
# ./mstrdiag

As a result, we get the DAPL tool interface:

Overview of the MicroStrategy Diagnostics and Performance Logging tool

There is lots of information and settings here. Let's try to better understand what's going on.

First of all, there are two configurations available:

  • Diagnostics Configuration - allows us to choose the diagnostics message we want to write in the log
  • Performance Configuration - allows us to fine-tune performance logging

In the preceding screenshot, we have the Diagnostics Configuration tab. It has two available configurations:

  • CastorServer - information related to server-specific features
  • Machine Default - information related to the machine on which the current user is working

We never used Machine Default, that's why it is good to go with CastorServer. Three log destinations are available:

  • System log - in Linux we can find the system log in /var/log/messages or /var/adm/messages.
  • Console log - send the log to the default system debugging output. In Linux it is redirected to the stderr device.
  • File log - we can set any filename and destination.

In addition, we should know the other components of the DAPL tool:

  • Component - a MicroStrategy component that will write logs
  • Dispatcher - level of system activity

Let's imagine that we have a problem with subscriptions. We want to trace the scheduler by creating a new log file. We should find Distribution Service and enable a SchedulerTrace by choosing <New> as the file log:

Overview of the MicroStrategy Diagnostics and Performance Logging tool

It is important to restart the Intelligence Server after any changes in the DAPL tool.

As a result, we will get a new SchedulerTrace log file with information about schedules.

Let's look at Performance Configuration:

Overview of the MicroStrategy Diagnostics and Performance Logging tool

In terms of performance, we can measure different counters, such as how much time it takes for the CPU to run MicroStrategy functions or run reports.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset