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

KB11281: Unable to select multiple log files for different Performance Configuration Counters in MicroStrategy Diagnositcs and Performance Logging


Community Admin

• Strategy


This article explains that all Performance Counters logged from MicroStrategy Diagnostics Tools will get logged to one file.

SYMPTOM
 
Users choose different log files for each counter selected in the Performance Configuration tab in Strategy Diagnostics and Performance Logging tool. However, after saving, all counters are set back to the name of the last log file selected prior to the save:

ka04W000000OhRJQA0_0EM440000002BlT.gif

 
Consider the following example where a user selects the following counters and saves the changes:
 
DSSAnalyticalEngineServerTaskCPU Time (sec) ---- Testing_File0
 
DSSAnalyticalEngineServerTask Elapse Time (sec) ---- Testing_File1
 
After saving, the user notice that the file for the DSSAnalyticalEngineServerTask CPU(Sec) is reset to the last file selected before saving which is Testing_File1.
 
CAUSE
 
This is working as designed. Server Diagnostics Configuration can only log to one file.
 
ACTION
 
Specify a single filename that will be used to record all counters. The default location of this file is /Drive/Program files (x86)/Common Files/MicroStrategy/filename.csv. Note that this destination cannot be changed.
 
A column in the .csv file will be listed for each counter specified and will be logged in the order listed in the Server Diagnostics Configuration Editor. The following screen shot is obtained using the example above:

ka04W000000OhRJQA0_0EM440000002BlU.gif

 


Comment

0 comments

Details

Knowledge Article

Published:

May 19, 2017

Last Updated:

May 19, 2017