The following are known limitations of network logging in telemetry configurations:
Jamf web protection is incompatible with network logging in telemetry configurations on macOS 14 or earlier. Enabling network logging in telemetry configurations on computers with macOS 14 or earlier will automatically disable Jamf web protection.
Network logging in telemetry configurations does not collect process data for the following browsers: Safari, Google Chrome, Mozilla Firefox, Microsoft Edge, Brave, Opera, Vivaldi, Zen Browser, and The Browser (Arc/Dia). Excluding select internet browsers allocates system resources efficiently, simplifies telemetry data for analysis, and reduces data storage costs. The list of browsers excluded from network logging in telemetry configurations is subject to change.
End-user computers may temporarily lose network connectivity when the Jamf Protect agent is updated, causing interruptions for end users. If your environment uses network logging in telemetry configurations, Jamf recommends disabling automatic updates for Jamf Protect plans and manually deploying the Jamf Protect agent instead, during optimal non-work hours. If you use Jamf Pro, you can accomplish this by creating a policy to deploy the Jamf Protect agent and then configuring specific days and times in the client-side timing limitation settings of the General payload. For assistance, contact Jamf Support.