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:
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:
In the preceding screenshot, we have the Diagnostics Configuration tab. It has two available configurations:
We never used Machine Default, that's why it is good to go with CastorServer. Three log destinations are available:
/var/log/messages
or /var/adm/messages
.stderr
device.In addition, we should know the other components of the DAPL tool:
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:
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:
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.