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

KB482989: How to configure Intelligence Server running on Windows to send logging to a remote Telemetry Server


Frederick Kellerman

Cloud Support Expert I • MicroStrategy


This article discusses how to configure Intelligence Server running on Windows to send data to a non-local Telemetry Server

OVERVIEW
Consider a scenario where Strategy Intelligence Server is installed on Windows and users wish to enable logging through Telemetry Server (Messaging Services.) In certain cases, it may be desired to install Telemetry Server on a remote computer and configure logging through the remote Telemetry Server instead of the local Telemetry Server that is bundled with the installation of the Intelligence Server. For example, a user may have an existing installation of Intelligence Server on Windows but wants to use Telemetry Server installed on a Linux box in order to avoid the issue from KB441447.
The following steps describe how to direct Intelligence Server to send data to the remote Telemetry Server. The following steps will assume that Telemetry Server has already been installed remotely and the underlying services, Kafka and Zookeeper are running.
CONFIGURATION STEPS
1. Once Telemetry Server has been installed remotely run the following Command Manager outlines against the Intelligence Server on Windows to enable Messaging Services and logging through Telemetry Server. In the first outline  <Telemetry Server IP> and <Telemetry Server port> should be updated with the correct values respectively.


ALTER SERVER CONFIGURATION ENABLEMESSAGINGSERVICES TRUE CONFIGUREMESSAGINGSERVICES "bootstrap.servers:<Telemetry Server IP>:<Telemetry Server port>/batch.num.messages:5000/queue.buffering.max.ms:2000";


ALTER FEATURE FLAG "SENDING LOG TO MESSAGING SERVICES" ON;

2. On the Intelligence Server machine update the LogConsumer.properties file to point to the remote Telemetry Server. This is done by modifying the broker_hostname field. The default location of the LogConsumer.properties file is: C:\Program Files (x86)\MicroStrategy\Intelligence Server\KafkaConsumer
3. Restart the Intelligence Server and the Strategy Intelligence Server Log Consumer. Intelligence Server will now stream logging through the remote Telemetry Server. By default the log files will be written locally on the Intelligence Server in the following folder location:
C:\Program Files (x86)\Common Files\MicroStrategy\Log\DSSErrors\
 


Comment

0 comments

Details

Knowledge Article

Published:

March 21, 2019

Last Updated:

March 21, 2019