Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@Canthv0 address pipeline issues |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@Canthv0 build pipeline failed. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| $OriginalInformationPreference = $InformationPreference | ||
| $InformationPreference = 'Continue' |
There was a problem hiding this comment.
We should do this correctly by doing a try finally block, so this always gets set back correctly.
There was a problem hiding this comment.
Pull Request Overview
Initial implementation of a new PowerShell script for analyzing Exchange Online Message Tracking Logs (MTL). This tool helps engineers and customers with limited MTL experience understand message delivery issues by parsing detailed tracking logs and generating readable reports.
- Adds Get-EXOMTLReport.ps1 script with functions to import, validate, and analyze EXO MTL data
- Includes documentation explaining usage with Start-HistoricalSearch for EXO log collection
- Adds navigation entry and spell check updates to support the new tool
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| mkdocs.yml | Adds navigation entry for Get-EXOMTLReport documentation |
| docs/Transport/Get-EXOMTLReport.md | Documentation explaining script usage, parameters, and examples |
| Transport/Get-EXOMTLReport.ps1 | Main PowerShell script implementing MTL parsing and reporting functionality |
| .build/cspell-words.txt | Updates spell check dictionary with new terms used in the script |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| .\Get-EXOMTLReport -MTLPath C:\temp\MyMtl.csv | ||
| ``` | ||
| Generates a report to the default path from the file C:\Temp\MyMtl.csv. | ||
|
|
||
| ``` PowerShell | ||
| .\Measure-EmailDelayInMTL -MTLPath C:\temp\LargeMTL.csv -ReportPath C:\output -MessageID "<1231421231@server.contoso.com>" |
There was a problem hiding this comment.
The parameter name in the example is 'MTLPath' but the script defines it as 'MTLFile'. This inconsistency could confuse users.
| .\Get-EXOMTLReport -MTLPath C:\temp\MyMtl.csv | |
| ``` | |
| Generates a report to the default path from the file C:\Temp\MyMtl.csv. | |
| ``` PowerShell | |
| .\Measure-EmailDelayInMTL -MTLPath C:\temp\LargeMTL.csv -ReportPath C:\output -MessageID "<1231421231@server.contoso.com>" | |
| .\Get-EXOMTLReport -MTLFile C:\temp\MyMtl.csv |
Generates a report to the default path from the file C:\Temp\MyMtl.csv.
.\Measure-EmailDelayInMTL -MTLFile C:\temp\LargeMTL.csv -ReportPath C:\output -MessageID "<1231421231@server.contoso.com>"2 participants
Issue:
Starting to build a script like healthchecker but for EXO message tracking logs.
Reason:
Need to help engineers and customers that have little experience with MTLs determine what they mean.