![]() ![]() Sudo /opt/microsoft/omsagent/bin/service_control restartįor more information, go to the related solution in the Azure Marketplace. Save changes and restart the Azure Log Analytics agent for Linux service with the following command: replace workspace_id with real value of your Workspace ID (lines 14,15,16,19) If you would like to change the default port for zpa.conf make sure that it should not get conflict with default AMA agent ports I.e.(For example CEF uses TCP port 25226 or 25224)ĭ. Ensure this port is not being used by any other source on your serverĬ. ![]() Step 3 Wait for the VPN to connect, then enjoy increased online privacy. Step 2 Alternatively, click the location bar to pick a specific location. specify port which you have set your Zscaler Log Receivers to forward logs to (line 4)ī. Step 1 Press the ‘On’ button to auto-connect to the nearest server. Login to the server where you have installed Azure Log Analytics agent.Ĭopy zpa.conf to the /etc/opt/microsoft/omsagent/ workspace_id/conf/omsagent.d/ folder.Ī. While configuring a Log Receiver, choose JSON as Log Template. Refer to LSS documentation for detailed informationĬonfigure Log Receivers. Zscaler Private Access logs are delivered via Log Streaming Service (LSS). Refer to the Azure Monitor Documentation for more details on these steps. Logs from Zscaler Private Access Server deployed on Linux or Windows servers are collected by Linux or Windows agents.įollow the configuration steps below to get Zscaler Private Access logs into Microsoft Sentinel. Install the agent on the Server where the Zscaler Private Access logs are forwarded. Install and onboard the agent for Linux or Windows.This data connector has been developed using Zscaler Private Access version: 21.67.1 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |