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

How to manually check which MicroStrategy components are sending data to Telemetry Server in MicroStrategy 2019


David Currin

Quality Engineer, Senior • MicroStrategy


Description

Beginning in Strategy 10.5 (on Linux) and 10.6 (on Windows), Strategy Telemetry Server (previously known as Strategy Messaging Services) uses the third-party Kafka framework to handle the DSSErrors logging output from the Intelligence Server process.  Strategy Platform Analytics, introduced in Strategy 11.0, also uses Telemetry Server to handle the Intelligence Server statistics output and processing.  Since Telemetry Server is built on the Kafka framework, some common troubleshooting tasks may be accomplished using scripts that are provided out-of-the-box with the Kafka installation.  One such task is checking which Strategy components a given Telemetry Server is receiving data from.
 

Application

In Kafka terminology, Strategy components that generate data to be sent to Telemetry Server are considered Producers, and the Telemetry Server itself is considered a Broker.  When a Producer sends data to a Broker, it categorizes the data into one or more Topics.  In Strategy, each Intelligence Server that is sending DSSErrors logging output to Telemetry Server will create a separate topic for this logging output in the format of:


Mstr.AnalyticsServer.Diag.<hostname>.CastorServer

Additionally, if any Intelligence Servers are sending statistics output to Telemetry Servers, a set of topics for Platform Analytics will be created. View the set of topics listed below for reference:

Mstr.PlatformAnalytics.ChangeJournal.AttributesAndForms
Mstr.PlatformAnalytics.ChangeJournal.Columns
Mstr.PlatformAnalytics.ChangeJournal.CubesReportsDossier
Mstr.PlatformAnalytics.ChangeJournal.DBConnection
Mstr.PlatformAnalytics.ChangeJournal.DBLogin
Mstr.PlatformAnalytics.ChangeJournal.DBRole
Mstr.PlatformAnalytics.ChangeJournal.FactsAndMetrics
Mstr.PlatformAnalytics.ChangeJournal.Folder
Mstr.PlatformAnalytics.ChangeJournal.Others
Mstr.PlatformAnalytics.ChangeJournal.Project
Mstr.PlatformAnalytics.ChangeJournal.PromptsConsolidationAndCustomGroups
Mstr.PlatformAnalytics.ChangeJournal.ScheduleEvent
Mstr.PlatformAnalytics.ChangeJournal.ScheduleTrigger
Mstr.PlatformAnalytics.ChangeJournal.SecurityFilter
Mstr.PlatformAnalytics.ChangeJournal.SecurityRole
Mstr.PlatformAnalytics.ChangeJournal.ServerDef
Mstr.PlatformAnalytics.ChangeJournal.Tables
Mstr.PlatformAnalytics.ChangeJournal.User
Mstr.PlatformAnalytics.ChangeJournal.UserGroup
Mstr.PlatformAnalytics.DistributionServices.Subscriptions
Mstr.PlatformAnalytics.Geolocation
Mstr.PlatformAnalytics.IsCacheHitStats
Mstr.PlatformAnalytics.IsCubeRepStats
Mstr.PlatformAnalytics.IsDocumentStats
Mstr.PlatformAnalytics.IsDocumentStepStats
Mstr.PlatformAnalytics.IsInboxActionsStats
Mstr.PlatformAnalytics.IsMessageStats
Mstr.PlatformAnalytics.IsProjectSessionStats
Mstr.PlatformAnalytics.IsPromptAnswerStats
Mstr.PlatformAnalytics.IsReportSQLStats
Mstr.PlatformAnalytics.IsReportSecurityFilterStats
Mstr.PlatformAnalytics.IsReportStats
Mstr.PlatformAnalytics.IsReportStepStats
Mstr.PlatformAnalytics.IsScheduleStats
Mstr.PlatformAnalytics.IsSessionStats
Mstr.PlatformAnalytics.LicenseAuditorContactsTelemetry
Mstr.PlatformAnalytics.LicenseAuditorTelemetry
Mstr.PlatformAnalytics.LicenseTelemetry
Mstr.PlatformAnalytics.RemoteDiagnostics.CPULicense
Mstr.PlatformAnalytics.RemoteDiagnostics.EnvironmentConfig
Mstr.PlatformAnalytics.RemoteDiagnostics.UserLicense

Thus, checking the list of topics that are registered with Telemetry Server can indicate which Intelligence Servers are sending DSSErrors logging information to it, and whether any Intelligence Servers are sending statistics.  In order to check the topics registered, an out-of-the-box Kafka script may be run from the Telemetry Server machine. 
The scripts are located in <MSTR_INSTALL>/MicroStrategy/MessagingServices/Kafka/kafka_2.11-1.1.0/bin on Linux, and \Program Files (x86)\MicroStrategy\Messaging Services\Kafka\kafka_2.11-1.1.0\bin\windows on Windows. 
The specific script to run is kafka-topics.sh (or kafka-topics.bat on Windows), with the following syntax:

./kafka-topics.sh --list --zookeeper localhost:2181

This will return the list of all topics currently registered on the Telemetry Server.  Some topics other than discussed above will also be present and may be disregarded as these are used for internal Strategy functions.

Learning Resources


Interested in learning more about Platform Analytics? Visit the Learning Center on Community!
Or feel free to go to our Documentation pages for product information.
 


Comment

0 comments

Details

Knowledge Article

Published:

December 21, 2018

Last Updated:

August 19, 2019