Cisco Cisco Web Security Appliance S380 Guida Utente

Pagina di 91
F I X E D   I S S U E S ,   K N O W N   I S S U E S ,   A N D   L I M I T A T I O N S
C H A P T E R   1 :   I N T R O D U C T I O N   T O   S A W M I L L   F O R   I R O N P O R T
 15
F I X E D   I S S U E S ,   K N O W N   I S S U E S ,   A N D   L I M I T A T I O N S
Fixed: Inaccurate Page View Statistics
The Page View calculations have been improved in Sawmill for IronPort version 7.3.1. 
Previously, the Page View statistics within various reports included data that was not 
necessary to make an accurate count of page views, such as entries for all responses. Now, 
Page View statistics use a filter to ignore all dropped or blocked client requests as well as 
server responses 1xx, 3xx, 4xx, and 5xx, none of which return data to the requested client. 
However, image files are incorporated into the Page View calculations. [Defect ID: 50257]
Fixed: Log Entries Containing Spaces in Usernames Do Not Appear in Reports
Previously, Sawmill for IronPort ignored log entries containing usernames with two or more 
elements with space between them. For example, log entries for the user “barack 2” would 
not appear in reports. This issue has been resolved. [Defect ID: 50075]
Fixed: HR Profile Erroneously Displays a “FIELD: Auth User” Report
Although the HR profile does not contain an Auth User field, the profile displays a FIELD: 
Auth User report. Please ignore this report in the HR profile. [Defect ID: 49697]
Fixed: Scheduling Database Updates in the Sawmill CLI Can Cause Sawmill for IronPort 
to Crash
Using the Sawmill CLI to schedule database updates can cause Sawmill for IronPort to crash. 
Workaround: Use the Sawmill GUI to schedule database updates.
[Defect ID: 48356]
Fixed: Importing Access Logs Can Cause Sawmill for IronPort to Crash
Importing or updating the access logs can cause Sawmill for IronPort to crash. 
Workaround: Import or update the access logs with a single processor, or set the Log 
Processing Threads in the Configuration Master file to 0.
[Defect ID: 55020]
Fixed: Updating the Database in Sawmill for IronPort May Throw an Application Error at 
the End of the Update
When you update the database, Sawmill for IronPort may throw an application error at the 
end of the update. This occurs regardless of the Log Processing Thread settings. However, the 
update has been successful, and no data corruption has occured.
[Defect ID: 52227]
Fixed: Sawmill for IronPort Discards Session that are Over Two Hours Long
Sawmill for Ironport discards all work sessions that are over two hours long. The default 
session length for Sawmill for Ironport is a maximum of two hours.
WSA_Sawmill.book  Page 15  Monday, March 15, 2010  10:31 AM