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

KB18642: How to turn off diagnostics logging for MicroStrategy components from the command line in Windows and Unix/Linux environments


Community Admin

• Strategy


How to turn off diagnostics logging for MicroStrategy components from the command line in Windows and Unix/Linux environments

Diagnostics logging can be turned on from the command line in both Windows and Unix / Linux environments. The process for enabling diagnostics logging using the MSTRCTL utility is described in the following Strategy Knowledge Base technical note:
 
KB15868 (KB5303-81x-2506): How to modify diagnostics logging for Strategy components from the command line in Windows and Unix/Linux environments
 
On the Strategy Intelligence Server 8.x machine, follow the steps below:
 

  1. Run the command 'mstrctl -s IntelligenceServer gsic'. This will output the current diagnostics and performance monitoring configuration in XML format.
  2. Run 'mstrctl -s IntelligenceServer ssic'. This will start input mode where new XML tags can be entered to replace the current configuration. In the example that follows, the 'Database Classes' component 'Error' dispatcher logging is turned off:
    <?xml version="1.0"?>
    <configuration>
    <diagnostics>
    <logger n="Database Classes">
    <dispatcher n="Error">
    <log_destination n="DebugOutput" delete="1"/>
    <log_destination n="DSSErrors" delete="1"/>
    </dispatcher></logger>
    </diagnostics>
    </configuration>
  3. Press 'Ctrl+d' in Unix and 'Ctrl+Z' in Windows to stop input and write changes.

In order to turn off other tracing components, modify this sample code accordingly, placing the tag <log_destination n="XXX" delete="1"/> where needed.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 13, 2017

Last Updated:

April 13, 2017