Message tracking logs contain data from the agents involved in processing the mail flow content. For DLP, the transport rule agent (TRA) is used to invoke deep message content scanning and to apply the policies defined as part of the ETRs. The existing AgentInfo Event is used to add DLP related entries in the message tracking log.

The agent name will be TRA or Transport Rule Agent in the AgentInfo event. A single AgentInfo event will be logged per message describing the DLP processing applied to the message. The CustomData field of the message tracking log entry field is where the DLP data logged by the transport rule agent will appear. This field may contain multiple entries: one data classification and client information line for each data classification found in the message, one rule line for each rule that applies to the message, and one health monitoring line for each rule that exceeds the load or execution time threshold.

An example of the DLP log entry is displayed here. The output has been formatted to display strings in separate lines with new lines between.

Source: AGENT

EventId: AGENTINFO

CustomData: S:TRA=DC|dcid=41BFDBC6C9D811E0816A3CD34824019B|count=10|conf=77;

S:TRA=DC|dcid=C7ECCBA0CA0011E0B6C00B124924019B|count=3|conf=81;

S:TRA=CI|sndOverride=or|just=Business Reason;

S:TRA=CI|sndOverride=fp;

S:TRA=ETR|ruleId=FC2AA60C9D811E0AFC076D34824019B|dlpid=1B81CC82C9DB11E09052C5D64824019B|st=2010-11-03 15:30T|action=PrependSubject|action=Encrypt|sev=2|mode=audit|dcid=41BFDBC6C9D811E0816A3CD34824019B|sndOverride=or;

S:TRA=ETR|ruleId=AB2AA60C9D811E0AFC076D34824019B|dlpid=1B81CC82C9DB11E09052C5D64824019B|st=2010-11-03 15:30T|action=Encrypt|sev=1|mode=enabled|dcid=C7ECCBA0CA0011E0B6C00B124924019B|sndOverride=fp;

S:TRA=ETRP|ruleId=C27D21EECA0311E0BCB896154924019B|LoadW=200|LoadC=100|ExecW=5500|ExecC=200;

The Transport Rule Agent requires grouping of the rule ID, DLP Policy ID (optional), last modified date, action, severity, mode, detected data classification (optional), and sender override (optional) based on rule ID (indicated by “TRA=ETR” in the log line). It also requires the data classification ID, count, and confidence level of classifications to be grouped by classification name (indicated by “TRA=DC” in the log line).

Additional groupings include data classification ID, sender override (optional), and override justification (optional) based on data classification ID for all classifications that were detected on the client (indicated by “TRA=CI” in the log line). The Transport Rule Agent also requires the rule ID, load Wall clock (optional), load CPU clock (optional), execution Wall clock (optional), and execution CPU clock (optional) be grouped by rule ID for all rules that exceed the load or execution Wall or CPU clock thresholds (indicated by “TRA=ETRP” in the log line).

The following is a complete list of the data fields. All data in the MTL is type string. Format column describes how to recognize each field in the Message Tracking Log. Optional Field column specifies what fields might not be logged when a rule matches. DLP Specific column shows what fields are specific to the DLP feature.

Field name	Description	Format	Optional field	DLP specific
TRA	Transport Rule Agent; type AgentName	TRA=DC, ETR, CI, or ETRP	Mandatory	No
DC	Data Classification; type groupName	TRA=DC	Optional	Yes
ETR	Exchange Transport Rule; type groupName	TRA=ETR	Mandatory	No
CI	Client Information, type groupName	TRA=CI	Optional	Yes
ETRP	Exchange Transport Rule Performance; type groupName	TRA=ETRP	Optional	No
dcid	ID of the Data Classification	dcid=GUID	Optional	Yes
count	Count of the Data Classification	count=Integer	Optional	Yes
conf	Confidence level of the Data Classification	conf=Integer (Percent)	Optional	Yes
sndOverride	Sender override; the field is optional. In the TRA=CI line, when field is set to “or” signifies the data classification was overridden. If the field is set to “fp” signifies the data classification was reported as a false positive. In the TRA=ETR line, when the field is set to “or” signifies the rule or part of the rule was overridden. If the field is set to “fp” signifies the rule or part of the rule was reported as a false positive.	sndOverride=or or fp Where “or” represents override and “fp” means false positive. The sndOverride field is present when an end-user had reported either an override or false positive for a rule.	Optional	Yes
just	Justification; the field is optional and only available when the sender override field is equal to “or” in the TRA=CI line. Justification text provided by the end user as the reason the data classification should be overridden.	just=IW input justification string Justification field is only logged when end user reports an override.	Optional	Yes
ruleId	ID for a rule	ruleId=GUID	Mandatory	No
dlpId	ID for a DLP Policy. The field is optional; if there is no dlpId then the rule doesn’t belong to a DLP Policy.	dlpId=GUID	Optional	Yes
st	Last Modified Date of a rule	st=UTC date-time	Mandatory	No
action	Action taken by a rule; could have multiple actions per rule	action=single action If there are multiple actions applied for a rule, there will be multiple action fields.	Mandatory	No
sev	Audit severity of the rule	sev=1, 2, or 3 Where 1 represents low, 2 is medium, and 3 means high.	Optional	No
mode	State of the rule when it was hit (enforcement, audit, or auditandnotify).	mode=audit, auditandnotify, or enforcement	Mandatory	No
loadW	Load Wall Clock; the field is optional	loadW=time in ms	Optional	No
loadC	Load CPU Clock; the field is optional	loadC=time in ms	Optional	No
execW	Execute Wall Clock; the field is optional	execW=time in ms	Optional	No
execC	Execute CPU Clock; the field is optional	execC=time in ms	Optional	No
message-id	ID of the message	message-id=ID of message	Mandatory	No
date-time	Date and time the message was sent in universal time	date-time=UTC date-time	Mandatory	No
sender-address	Email address specified in the sender field	sender-address=Email address	Mandatory	No
recipient-address	Email address(es) of the message’s recipient(s)	recipient-address=Email address	Mandatory	No
message-subject	Data found in the subject field of the message	message-subject=end-user input subject string	Mandatory	No