Add RESTLogs collection to Exchange Log Collector#2552
Merged
Conversation
Add -RESTLogs switch to collect REST API logs from both backend (Logging\Rest) and proxy (Logging\HttpProxy\Rest) directories, following the same pattern as EWSLogs. Included in -AllPossibleLogs. Fixes #2123 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds first-class collection support for Exchange REST API logs in the Exchange Log Collector, improving troubleshooting data capture for Exchange–Teams REST integration scenarios.
Changes:
- Added
-RESTLogsswitch toExchangeLogCollector.ps1and propagated it through argument passing to remote collection. - Included
RESTLogsin the “all possible logs” scenario and in the “no switches provided” guard logic. - Implemented remote collection logic for both backend (Mailbox) and proxy (CAS) REST log directories and documented the new switch.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| docs/Diagnostics/ExchangeLogCollector.md | Documents the new RESTLogs parameter and its log locations. |
| Diagnostics/ExchangeLogCollector/RemoteScriptBlock/Invoke-RemoteMain.ps1 | Adds remote collection actions for backend and proxy REST log paths based on server role. |
| Diagnostics/ExchangeLogCollector/Helpers/Test-PossibleCommonScenarios.ps1 | Ensures -AllPossibleLogs enables REST log collection. |
| Diagnostics/ExchangeLogCollector/Helpers/Test-NoSwitchesProvided.ps1 | Treats -RESTLogs as a “switch provided” to avoid the no-switch warning path. |
| Diagnostics/ExchangeLogCollector/Helpers/Get-ArgumentList.ps1 | Passes RESTLogs through to the remote scriptblock via the argument object. |
| Diagnostics/ExchangeLogCollector/ExchangeLogCollector.ps1 | Introduces the -RESTLogs switch parameter. |
lusassl-msft
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
-RESTLogsswitch to the Exchange Log Collector to collect REST API logs, enabling troubleshooting of Exchange-Teams integration scenarios.Log Directories Collected
%ExchangeInstallPath%Logging\Rest%ExchangeInstallPath%Logging\HttpProxy\RestChanges
[switch]$RESTLogsparameter toExchangeLogCollector.ps1-AllPossibleLogsscenarioGet-ArgumentListInvoke-RemoteMain.ps1follows the same Mailbox/CAS dual-path pattern asEWSLogsFixes #2123