142
C
HAPTER
9: M
ONITORING
W
EB
A
CCESS
alphanumeric and
.
(dot),
-
(hyphen) or
_
(underscore) characters and can
only be up to 32 characters in length.
Clicking
FTP Now
will immediately send the currently active Access Log to
the FTP server. This allows you to test your FTP settings or to save the
Access Log without waiting for the next automatic FTP.
If no entries have been made in the logs when you click
FTP Now
, an
empty log file will be saved on the FTP server.
Viewing the Access
Log
To view the Access Log using the Web interface:
1
Log in to the Web interface.
2
Click
Caching
on the Toolbar.
3
Select
View Access Log
in the Navigation Tree.
The last 256 lines of the Access Log are displayed, with the most recent
information shown at the bottom of the log.
4
Click
Refresh
to update the displayed information.
If the Webcache is deployed in Proxy mode, multiple entries for the pages
in the Web interface itself will be made in the Access Log. This is standard
behavior for the Webcache, as it is “seeing” the requests for the Web
interface pages and logging these requests in the Access Log. You should
either leave the Web Interface open for only short periods of time to
reduce the entries made, or use a log analyzer tool such as Webtrends to
view and analyze the Access Log.
Analyzing the
Access Log
The access logs that have been saved on the FTP server are by default
based on the native Squid Log format. This is optimized for efficient
generation and can be analyzed using a wide variety of off-the-shelf log
analysis tools.
3Com recommends that you select the Webtrends Extended Log Format
(WELF) option and use Webtrends Log Analyzer or WebTrends Firewall
Suite to analyze the access logs that the Webcache produces:
http://www.webtrends.com
(correct at time of publication)
dua1611-5aaa04.book Page 142 Friday, November 29, 2002 8:56 PM
Summary of Contents for SUPERSTACK 3 WEBCACHE 3000
Page 16: ...dua1611 5aaa04 book Page 16 Friday November 29 2002 8 56 PM...
Page 22: ...22 dua1611 5aaa04 book Page 22 Friday November 29 2002 8 56 PM...
Page 80: ...80 dua1611 5aaa04 book Page 80 Friday November 29 2002 8 56 PM...
Page 110: ...110 dua1611 5aaa04 book Page 110 Friday November 29 2002 8 56 PM...
Page 136: ...136 CHAPTER 8 SYSTEM TIME dua1611 5aaa04 book Page 136 Friday November 29 2002 8 56 PM...
Page 138: ...138 dua1611 5aaa04 book Page 138 Friday November 29 2002 8 56 PM...
Page 180: ...180 dua1611 5aaa04 book Page 180 Friday November 29 2002 8 56 PM...
Page 204: ...204 CHAPTER 12 PRELOADING CONTENT dua1611 5aaa04 book Page 204 Friday November 29 2002 8 56 PM...
Page 206: ...206 dua1611 5aaa04 book Page 206 Friday November 29 2002 8 56 PM...
Page 234: ...234 dua1611 5aaa04 book Page 234 Friday November 29 2002 8 56 PM...
Page 248: ...248 CHAPTER 17 SOFTWARE UPGRADES dua1611 5aaa04 book Page 248 Friday November 29 2002 8 56 PM...
Page 250: ...250 dua1611 5aaa04 book Page 250 Friday November 29 2002 8 56 PM...
Page 274: ...274 dua1611 5aaa04 book Page 274 Friday November 29 2002 8 56 PM...
Page 286: ...286 dua1611 5aaa04 book Page 286 Friday November 29 2002 8 56 PM...
Page 294: ...294 APPENDIX A SAFETY INFORMATION dua1611 5aaa04 book Page 294 Friday November 29 2002 8 56 PM...
Page 348: ...348 GLOSSARY dua1611 5aaa04 book Page 348 Friday November 29 2002 8 56 PM...