EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB46316: How to enable recommended performance counter logging for MicroStrategy server instances from the command line using MSTRCTL command in MicroStrategy Intelligence Server Universal


Community Admin

• Strategy


Guided steps to use mstrctl utility to enable recommended performance counters.

The MSTRCTL utility can be used to enable performance counter logging for Strategy server instances from the command line. This utility is described in the following Strategy Knowledge Base technical note: KB10941: What is the MSTRCtl utility and how is it used in MicroStrategy Intelligence Server 9.x - 10.x
The following steps will enable logging for the performance counters outlined in the following Strategy Knowledge Base technical note: 
KB19155: Recommended performance logging counters to enable when troubleshooting memory or performance issues in MicroStrategy Intelligence Server Universal 9.x in UNIX environments
On the Strategy Intelligence Server 9.x - 10.x machine:

  1. Run the command './mstrctl -s IntelligenceServer ssic' from the bin folder to set a new configuration for the Strategy Intelligence Server performance configuration.
  2. Copy, paste, and execute the following XML script into the command line:
     

       <configuration n="CastorServer"> 
       <performance_counters log_destination="DSSPerformanceMonitor" pru="0" frequency="30" persist_perf_counter="1" log_statistics="1" stats_frequency="5">

    <cat n="Memory">
       <performance_counter n="Free paging space(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Free real memory(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Reserved paging space(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total paging space(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total real memory(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Used real memory(MB)" persist="1" persist_to_stats="0"/>
    </cat>
    <cat n="Process">
       <performance_counter n="% CPU time" persist="1" persist_to_stats="0"/>
       <performance_counter n="RSS(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Size(MB)" persist="1" persist_to_stats="0"/>
    </cat>
    <cat n="Processor">
       <performance_counter n="% Idle Time" persist="1" persist_to_stats="0"/>
       <performance_counter n="% System Time" persist="1" persist_to_stats="0"/>
       <performance_counter n="% User Time" persist="1" persist_to_stats="0"/>
       <performance_counter n="% Wait Time" persist="1" persist_to_stats="0"/>
       <performance_counter n="Number of active CPUs" persist="1" persist_to_stats="0"/>
    </cat>
    <cat n="System">
       <performance_counter n="RAM used(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Swap used(MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total CPU" persist="1" persist_to_stats="0"/>
       <performance_counter n="Virtual memory used(MB)" persist="1" persist_to_stats="0"/>
    </cat>
    <cat n="Strategy Server Jobs">
       <performance_counter n="Executing Reports" persist="1" persist_to_stats="0"/>
       <performance_counter n="Memory Used by Report Caches (MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Open Reports" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total Documents" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total Local Cube Cache Size (MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total Local Document Cache Size (MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total Local Report Cache Size (MB)" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total in-use memory (KB) in server process heap" persist="1" persist_to_stats="0"/>
       <performance_counter n="Total cached memory (KB) in the server process heap" persist="1" persist_to_stats="0"/>
    </cat>
    <cat n="Strategy Server Users">
       <performance_counter n="Open Sessions" persist="1" persist_to_stats="0"/>
       <performance_counter n="Open Project Sessions" persist="1" persist_to_stats="0"/>
       <performance_counter n="Working set cache RAM usage" persist="1" persist_to_stats="0"/>
    </cat>
     
    </performance_counters>
    </configuration>


     
  3. The user needs to key in the 'Ctrl+D' sequence on UNIX/Linux and 'Ctrl+Z' in Microsoft Windows platforms to stop input and write changes to the server configuration.  The XML tag explanations can be found in the following Strategy Knowledge Base technical note:
    KB16605: How to enable/disable performance counter logging for MicroStrategy server instances from the command line using MSTRCTL command in MicroStrategy Intelligence Server 9.x and 10.x
     
  4. To confirm that the correct performance counters have been enabled, run the command './mstrctl -s IntelligenceServer gsic' from the bin folder.
  5. Users will need to restart the Strategy Intelligence Server instance to start logging the recommended counters.  Upon restarting, the DSSPerformanceMonitor file will be created as a CSV file located in the same folder as the DSSErrors log.

NOTE: MSTRCTL write modifications to the MSIReg.reg file.  A restart is required to force the server to read the new values from MSIReg.reg
 
To disable logging, users should use the same XML script above, and modify each performance counter line from
 
   <performance_counter n="Free paging space(MB)" persist="1" persist_to_stats="0"/>
 
To:
   <performance_counter n="Free paging space(MB)" persist="0" persist_to_stats="0"/>
 
 
Again, users will need to restart the Strategy Intelligence Server instance for changes to take affect.
Alternatively users can enable the new performance logging configuration, users should run the command 'echo "p" > <MSTR_HOME_PATH>/IntelligenceServer/command-iserver.txt' at the command line. If that does not work a restart will be required.


Comment

0 comments

Details

Knowledge Article

Published:

July 18, 2017

Last Updated:

August 29, 2017