The Bandwidth Control policy specifies how an organization's bandwidth is allocated. You can add rules that prioritize business-critical apps and ensure that recreational or non-business critical applications do not affect productivity. It contains a default rule, which you can edit, but not delete. To learn more, see About Bandwidth Control.
You can also define the bandwidth classes that you want to include in the Bandwidth Control policy before you add rules to the policy or while you're adding the rules. To learn more, see About Bandwidth Classes.
To see how this policy fits into the overall order of policy enforcement, see How does the Zscaler service enforce policies?
To configure the Bandwidth Control policy of a location:
You can then go to the Bandwidth Control dashboard to view your organization's bandwidth usage in real time or go to Analytics > Interactive Reports to view the Bandwidth Control standard reports.
Specify the maximum upload and download bandwidth limits for each location in your organization. About 5% - 7% of TCP traffic is overhead, such as packet headers. The Zscaler service does not include these in its bandwidth calculations. It only includes the application traffic that is proxied to Zscaler. Therefore, the best practice for computing a location's bandwidth is as follows:
Actual bandwidth – (10% - 15% overhead) = Upload and Download bandwidth.
To enable bandwidth control for the location:
There are some additional features to be aware of when adding rules to sub-locations: