From d303c9f321227cde756c4bbdc111f972e40eaeba Mon Sep 17 00:00:00 2001 From: shchoud Date: Tue, 4 Nov 2025 21:00:57 +0530 Subject: [PATCH 1/2] Enhance troubleshooting guidance with diagnostic script info Added a note about the Log Collector Diagnostic script for troubleshooting. --- defender-for-cloud-apps/troubleshooting-cloud-discovery.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/defender-for-cloud-apps/troubleshooting-cloud-discovery.md b/defender-for-cloud-apps/troubleshooting-cloud-discovery.md index cb6bab13f5..ba21250454 100644 --- a/defender-for-cloud-apps/troubleshooting-cloud-discovery.md +++ b/defender-for-cloud-apps/troubleshooting-cloud-discovery.md @@ -52,6 +52,8 @@ You can track the processing of cloud discovery logs using the governance log. T |----|----| |Discovery data was uploaded and parsed successfully but the cloud discovery dashboard looks empty|The Dashboard might be filtered on data your logs don't have so there's no data to show. Try changing the filters in the cloud discovery dashboard to show different types of data to see the results.| +[Log collector Diagnostic script](https://github.com/microsoft/Microsoft-Defender-for-Cloud-Apps/tree/main/Sample%20scripts/Log-Collector-Diag-Script) automates the collection and compression of logs and diagnostic data for troubleshooting Log Collector containers on Linux (Docker/Podman), improving workflow efficiency. If contacting support, please run the script and share the generated log bundle for faster resolution + ## Next steps > [!div class="nextstepaction"] From cb9430986fd89442107eafaae540081c0948b6c9 Mon Sep 17 00:00:00 2001 From: AbbyMSFT <88824859+AbbyMSFT@users.noreply.github.com> Date: Mon, 10 Nov 2025 13:27:42 +0200 Subject: [PATCH 2/2] Update defender-for-cloud-apps/troubleshooting-cloud-discovery.md --- defender-for-cloud-apps/troubleshooting-cloud-discovery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/defender-for-cloud-apps/troubleshooting-cloud-discovery.md b/defender-for-cloud-apps/troubleshooting-cloud-discovery.md index ba21250454..03c82f4284 100644 --- a/defender-for-cloud-apps/troubleshooting-cloud-discovery.md +++ b/defender-for-cloud-apps/troubleshooting-cloud-discovery.md @@ -52,7 +52,7 @@ You can track the processing of cloud discovery logs using the governance log. T |----|----| |Discovery data was uploaded and parsed successfully but the cloud discovery dashboard looks empty|The Dashboard might be filtered on data your logs don't have so there's no data to show. Try changing the filters in the cloud discovery dashboard to show different types of data to see the results.| -[Log collector Diagnostic script](https://github.com/microsoft/Microsoft-Defender-for-Cloud-Apps/tree/main/Sample%20scripts/Log-Collector-Diag-Script) automates the collection and compression of logs and diagnostic data for troubleshooting Log Collector containers on Linux (Docker/Podman), improving workflow efficiency. If contacting support, please run the script and share the generated log bundle for faster resolution +The [Log collector Diagnostic script](https://github.com/microsoft/Microsoft-Defender-for-Cloud-Apps/tree/main/Sample%20scripts/Log-Collector-Diag-Script) automates the collection and compression of logs and diagnostic data for troubleshooting Log Collector containers on Linux (Docker/Podman) to improve workflow efficiency. If you need to contact support, run the script and share the generated log bundle for faster case resolution. ## Next steps