PDF(6.3 KB) View with Adobe Reader on a variety of devices
ePub(66.8 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(67.0 KB) View on Kindle device or Kindle app on multiple devices
Updated:June 5, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Since every customer environment varies, it is recommended to gather baseline production statistics over a set period of time in order to see if there are any outliers during the baseline period. During this baseline, note periods when client requests/second where maximized. If there was a corresponding drastic increase in response time and potential CPU usage, this could represent the peak performance in this specific environment. Further testing and monitoring should be performed in order to confirm this maximum level.
After the baseline period has elapsed, and no specific maximum peaks have been observed in client requests /second, it is recommend to artificially set a threshold value of 10% to 25% of the highest observed client requests/second for alerting purposes.
Aside from monitoring performance and alerting on specific exceeded thresholds, the Cisco WSA can also be configured to send SNMP traps on these hardware conditions: