Skip to content

Commit bfee236

Browse files
authored
Added info about Log collector script to troubleshooting
Added information about the Log collector Diagnostic script for troubleshooting.
1 parent ddbcc69 commit bfee236

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

defender-for-cloud-apps/troubleshooting-cloud-discovery.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This article provides a list of cloud discovery errors and resolution recommenda
1212

1313
Even after Discovery is set up, customers might continue hardening the Operating System in order to meet compliance standards. However, this action might cause interference with the containerization service itself.
1414

15-
## Microsoft Defender for Endpoint integration
15+
## Microsoft Defender for Endpoint integration errors
1616

1717
If you integrated Microsoft Defender for Endpoint with Defender for Cloud Apps, and you don't see the results of the integration.
1818

@@ -37,6 +37,8 @@ You can track the processing of cloud discovery logs using the governance log. T
3737

3838
## Log collector errors
3939

40+
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.
41+
4042
|Issue|Resolution|
4143
|----|----|
4244
|Couldn't connect to the log collector over FTP| 1. Verify that you're using FTP credentials and not SSH credentials. <br />2. Verify that the FTP client you're using isn't set to SFTP (Secure File Transfer Protocol). |

0 commit comments

Comments
 (0)