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

KB440368: Messaging Service: New MicroStrategy Logging System


Zeena Husayni

Director, Cloud Migrations & Technical Account Management • MicroStrategy


For 10.5 and above release, MicroStrategy Messaging Service is enabled by default during installation.  It is a distributed publish/subscribe messaging system based on Apache Kafka.

Note: Starting in Strategy 11.0, the behavior has been changed and the Intelligence Server does not Messaging Services by default. For more details, see KB442160.
For 10.5 and above release, Strategy Messaging Service is enabled by default during installation.  It is a distributed publish/subscribe messaging system based on Apache Kafka.  Below graph shows the basic architecture of the Strategy Messaging Services and as one can tell, the Intelligence server is one of Kafka Producers with the 'I-server log Consumer' being its content consumer.  
Messaging Services Architect:

ka04W000001IsMQQA0_0EM44000000A5xb.png

Messaging Services Workflow for I-Server:

ka04W000001IsMQQA0_0EM44000000A5xg.png

*You can learn more about Kafka cluster from this page: https://www.tutorialspoint.com/apache_kafka/apache_kafka_cluster_architecture.htm
Impact on logs and traces:
With this new messaging system enabled in 10.5 and above, all Intelligence server logs and traces (i.e. logs from Diagnostics and Configuration Tool, DSSErrors.log etc,.)  will be logged, by default, to the following location, for example:

  • Windows: C:\Program Files (x86)\MicroStrategy\CommonFiles\MicroStrategy\Log\DSSErrors\DSSErrors.log
  • Linux: <LOG_PATH>/DSSErrors/DSSErrors.log


 However, if messaging service is disabled due to whatever reason (including any unexpected Kafka server downtime), then all logs and traces will be written to local disk (same location as prior to using messaging service), for example:

  • Windows: C:\Program Files (x86)\MicroStrategy\CommonFiles\MicroStrategy\Log\DSSErrors.log
  • Linux: <LOG_PATH>/DSSErrors.log


 
Impact on using existing metadata where messaging service was enabled: 
Let's assume I-server environment A is connected to metadata A with server definition A and message service is enabled and configured to log to location A.  You are asked to create Environment B with I-server B against a copy of metadata A: if the same server definition A is used in this environment B, all logs will be written to location A as well.  If this is not the desired behavior, please do disable message service ASAP when setting up environment B, make changes to desired logging path prior to enabling message service again. 
To enable/disable Kafka via Command Manager, please take a look at the following knowledge base article:
KB328864: How to enable and disable MicroStrategy Messaging Services (Kafka) logging for the Intelligence Server in MicroStrategy 10.5 and higher versions on Windows and Linux
To limit the file size of the messages being logged to Kafka, please take a look at the following article for Governing Requests:Limiting the Size of Messages Logged to Kafka
  KB440368


Comment

0 comments

Details

Knowledge Article

Published:

March 27, 2018

Last Updated:

February 9, 2021