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

KB45563: What is the "Summary" dispatcher for Distribution Services diagnostics and what is its purpose for MicroStrategy Distribution Services 9.x and newer?


Community Admin

• Strategy


This article explains what is the "Summary" dispatcher for Distribution Services diagnostics and what is its purpose for MicroStrategy Distribution Services 9.x and newer?

Starting in Strategy 9.x, additional logging is available for Distribution Services. The "Summary" dispatcher is useful when troubleshooting the job(s) that is/are created for a Distribution Services subscription. The dispatcher can be found in the Strategy Diagnostics and Performance Logging tool as shown below.
 

ka04W000000Odq2QAC_0EM4400000029UK.png

Note: This trace is not enabled by default. An existing or new "File Log" destination must be selected for this logging to be used.
When a schedule triggers the execution of one or more subscriptions, a job is created for Distribution Services. This dispatcher will log details about a scheduled event.
When a scheduler triggers a subscription event, a sample of entries logged by the trace are shown below:
2013-12-18 17:44:00.236-05:00 RETRIEVE 6 subscriptions in total for scheduler 'All the Time', execute 6 subscriptions on this node. <Scheduler Execution ID = F9BCAA734593813DC061C49AA5CA0A16>
This dispatcher provides detailed information about the scheduler's name, how many subscriptions were retrieved and executed by the scheduler, and the Scheduler Execution ID.
Note: The "Summary" dispatcher will not log an entry if the subscription was not successfuly delivered due to an invalid physical address or report execution failure.


Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2017

Last Updated:

June 15, 2017