Application Shielding is an opt-in product feature for all Webscale customers. This feature allows a controlled isolation of the application servers in a customer's cloud account, against traffic from the Internet. A handful of Webscale customers have requested to configure their application servers so the only HTTP/HTTPS traffic that reaches is through the Webscale proxy servers, and this feature was developed in response to that.

This filter exists primarily to ensure that other filters have a place to insert new tags that needs to be in the head, or that trigger on the closing-tag for a head to perform some other action.

The filter builder allows you to easily navigate records to find the specific traffic interactions that interest you. As stated in the using the traffic viewer article, the filter bar connects with each traffic view. There are many ways to build filters; some methods are dependent on if you are in a records or summary view.

The Traffic Viewer enables you to drill down to specific records and then step back to previous searches to investigate records elsewhere. You have the option to view traffic records in two formats: the detailed records view or the summarized grouping view.

Fixed a bug in acs-scavenger causing it to exit early in some cases, acs-scavenger now will no longer reap servers in monitored_lgips, acs monitored_lgips command shows all ips being monitored for inclusion in the IP database, acs servers command shows all cluster servers configured to for code sync, bug in atomic deployments scripts causing multiple references to the same cluster to crash the run.

The webscale-cli command is the Swiss army knife of Webscale commands. It can be used to fix permissions, restart servers, check the health of the cluster, and many other things.