Chat now with support
Chat mit Support

MessageStats 7.8 - Reports User Guide

Viewing, Creating, and Editing MessageStats Reports My Reports and Corporate Reports Exchange Executive Summaries Reports Exchange Organizations Reports Exchange Server Reports Exchange Content Analysis Reports Exchange Mailboxes Reports Exchange Mail Contacts Reports Exchange Distribution Groups Reports Exchange Public Folders Reports Exchange Storage Reports Exchange Internet Reports Exchange Inventory Reports Migration Reports MessageStats Gathering Reports Appendix A: How to Read the Reports Report Filter Definitions

Introducing MessageStats Gathering Reports

The MessageStats Gathering node contains reports with an administrative view of the MessageStats database and are not based on any Exchange server data.

These reports provide information on the gathering history of Exchange servers including summary information, status of gatherings, and gathering failures.

MessageStats Gathering Report Descriptions

The MessageStats Gathering report folder contain reports that describe the status of the various MessageStats gathering tasks.

 
Table 1. MessageStats Gathering Status reports.
Report
Description
Filters

Gathering Summary

This report shows the status of tasks performed by the MessageStats application and by the MessageStats Scheduler Service.

The status information also appears in the Gathering Status report that is accessible on the MessageStats Console. For more information, the MessageStats Administrator Guide.
•
Date
•
Source
•
Server/DAG
•
Server Roles
•
Organization

Gathering Status

This report presents a more detailed status of the tasks performed by MessageStats and by the MessageStats Scheduler Service. This report aggregates the task entries for each source.
•
Date
•
Source
•
Server/DAG
•
Server Roles
•
Organization

Gathering Failure

The Gathering Failure report provides a list of all the MessageStats gathering and processing tasks with the following statuses: Aborted, Failed, Pending, Processing, Pending Retry, and Warning. For information about gathering and processing task status, see the MessageStats Administrator Guide.

The report is grouped by status and provides you with a means to monitor and troubleshoot the gathering of data in your Exchange organizations.
•
Date
•
Status
•
Source
•
Server/DAG
•
Server Roles
•
Organization

Appendix A: How to Read the Reports

•
What is the Definition of Physical and Logical Messages?
•
Reports that Show Physical Message Counts
•
Reports that Show Logical Message Counts
•
How Does MessageStats Determine Internal and External Messages?
•
Viewed from a Server Perspective
•
Viewed from a Mailbox Perspective
•
Other Factors to be Considered
•
Internal and External Messages - Frequently Asked Questions
•
Differences Between Messages Submitted, Delivered, and Transferred In and Out
•
Sample Scenario: MessageStats Counts
•
Why Does the Date Filter Always Group Using UTC?

What is the Definition of Physical and Logical Messages?

MessageStats reports show the message values in two categories: logical and physical. In the report column headings, the term physical identifies the physical message counts. If messages are not labeled as physical, they are logical messages.

For example, in the Mailbox Activity | Summary report, the message columns are labeled as Physical Messages. The term physical message is used to provide message counts in a manner similar to how Exchange handles a message. When a user opens Outlook, creates a message with five recipients and clicks Send, there is one physical message that Exchange tries deliver to each recipient.

Exchange may create copies of the message so that each recipient can receive the message. This process is called bifurcation and is performed when different recipients receive copies of the same message. A logical message is a message in which each recipient is counted as a separate message. For example, if a mail message is created in Outlook and is sent to nine recipients, MessageStats would count that as one physical sent message and nine logical sent messages. From a delivery standpoint (received messages), the logical and physical counts are the same since a delivery event can only happen to one mailbox.

Logical message counts make more sense when you categorize messages as internal or external. For example, in the Mailbox Activity | Internal vs. External report, MessageStats needs to determine whether a mailbox is sending internal or external messages. Since a message can have multiple recipients, and the recipients can be both internal and external, reports need to show a message in more granular way.

For information about internal and external messages, see How Does MessageStats Determine Internal and External Messages? .

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen