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
  3. KB413330: What are the Logging Levels for MicroStrategy Narrowcast Server 9.x?

KB413330: What are the Logging Levels for MicroStrategy Narrowcast Server 9.x?


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article contains information about the various logging levels available for MicroStrategy Narrowcast.

LEVEL_CRITICAL_ERROR 

Complete system failure, EX. The inability of the Narrowcast Server system to function. The failure of a sole running Distribution Manager (no backup), loss of connection to the repository. (Default – 1)

LEVEL_SEVERE_ERROR

High level system failure, EX. Connection to Subscription Book Module is not established, Delivery Engine failed, Distribution Manager failed, No DNS on a machine (generally errors pertaining to an entire service) (Default – 1)

LEVEL_MODERATE_ERROR

Mid-level system error, EX. Information Source Manager, Information Transmission Module, Document Formatter Module failure (generally errors pertaining to multiple recipients, such as at the segment level) (Default – 1)

LEVEL_MINOR_ERROR

Lowest level system error. EX. Unable to send an email to a recipient, failure of an information object for a recipient (generally errors pertaining to a single recipient) (Default – 1)

LEVEL_STAT_EXECUTION

Service level tracking information (Default – 1)

LEVEL_STAT_SEGMENT

Segment level tracking information (Default – 1)

LEVEL_STAT_RECIPIENT

Recipient level tracking information (Default – 1)

LEVEL_DEBUG

Very low level diagnostic info used internally by Technology to analyze issues during development or where very detailed tracing information is needed to help diagnose any potential problems. Some components generate vast amounts of LEVEL_DEBUG information. (Default – 0)

LEVEL_INFO

Information relating to the general operation of Narrowcast Server. Any components that do not have their own specific Level_INFO_xxxx level will log at this level (such as the SMTP Service) (Default – 1)

LEVEL_INFO_DFM

General operational messages from the Document Formatter Module (Default – 1)

LEVEL_INFO_DM

General operational messages from the Distribution Manager EX. System Startup/Shutdown, high level notification of service execution (Default – 1)

LEVEL_INFO_EE

General operational messages from the Execution Engine (Default – 1)

LEVEL_INFO_ER

General operational messages from the Execution Recorder (Default – 1)

LEVEL_INFO_ISM

General operational messages from the Information Source Module (Default – 1)

LEVEL_INFO_ITM

General operational messages from the Information Transmission Module (Default – 1)

LEVEL_INFO_SBM

General operational messages from the Subscription Book Module (Default – 1)

LEVEL_INFO_SE

General operational messages from the Segment Executor (Default – 1)

LEVEL_TRACE

Low level functional tracing information. Any components that do not have their own specific LEVEL_TRACE_xxxx will log at this level (Default – 0)

LEVEL_TRACE_DFM

Low level tracing information for the Document Formatter Module (Default – 0)

LEVEL_TRACE_DM

Low level tracing information for the Distribution Manager (Default – 0)

LEVEL_TRACE_EE

Low level tracing information for the Execution Engine (Default – 0)

LEVEL_TRACE_ER

Low level tracing information for the Execution Recorder (Default – 0)

LEVEL_TRACE_ISM

Low level tracing information for the Information Source Module (Default – 0)

LEVEL_TRACE_ITM

Low level tracing information for the Information Transmission Module (Default – 0)

LEVEL_TRACE_SBM

Low level tracing information for the Subscription Book Module (Default – 0)

LEVEL_TRACE_SCH

Low level tracing information for the Scheduler – both the Distribution Manager and the GUI will generate messages at this level (the GUI uses the same Scheduler DLL as the Distribution Manager) – details Schedule construction, parameters passed to the scheduler from the repository as well as general execution flow details of the scheduler. Includes both local and UTC dates and times for most operations. (Default – 0)

LEVEL_TRACE_SE

Low level tracing information for the Segment Executor (Default – 0)

LEVEL_TRACE_SQL

Low level SQL tracing generated by the Narrowcast Server APIs (Default – 0)

LEVEL_TRX_RECORDER

Low level Transmission Recorder tracing information (Default – 0)

Other Notes:
  • The logging services may also generate debug messages to the debug viewer local to that machine.
  • The levels at which the MicroStrategy Narrowcast Server components log (as detailed above) are independent of the levels for which the Logging Consumer Service subscribes to (by default, all levels)
  • The OUTPUT_TO_DEBUG instructs the log consumer service to send all received messages to the debug viewer on that machine. Set to 1 to enable, 0 to disable
  • The OUTPUT_TO_FILE instructs the log consumer service to send all received messages to the cyclic log files on that machine. Set to 1 to enable, 0 to disable
  • The OUTPUT_TO_NT_EVENT_VIEWER instructs the log consumer service to send all received messages to the Event Log on that machine. Set to 1 to enable, 0 to disable.
  • The log consumer service must run on the same machine as the Logging Server
  • LEVEL_TRACE, LEVEL_TRACE_XXXX, LEVEL_DEBUG and LEVEL_STAT_RECIPIENT generate a significant amount of information - expect performance degradation and/or more CPU utilization
  • The logging consumer COM interface is detailed in the MicroStrategy Narrowcast Server documentation
  • All the logging components create their own registry keys if they do not exist - Only run them once and the keys will be created. The only key that is not created is the subkey of HKLM\Software\MicroStrategy Broadcast Server\7.0\ Distributed Logging Service\MLS Client Settings\MLS Servers\ that tells the Logging Client where to forward its messages to a Logging Server.

    This subkey is typically called 'Server 1', and is created by the cluster wizard. If users are debugging, they can drop these keys, create a new 'Server 1' key and its contents (the 3 values in there will be created and default to localhost, port 20020)

 

WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any MicroStrategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.
 KB413330


Comment

0 comments

Details

Knowledge Article

Published:

March 9, 2023

Last Updated:

January 31, 2024