Understanding Novell BorderManager's HTTP Proxy Logs
Novell Cool Solutions: Feature
By Marcus Williamson
|
Digg This -
Slashdot This
Posted: 11 Jan 2002 |
Current version: BorderManager 3.6
Don't miss this new AppNote by the resident genius from Connectotel Ltd (http://www.connectotel.com/). Marcus, we are proud to note, is a member of the BorderManager Cool Solutions Advisory Board, as well as the eDirectory Cool Solutions Advisory Board.
Introduction
The ability to create accurate log files is an important aspect of the operation of proxy software. Log files provide the following functionality for administrators and users of the proxy:
- Determine patterns of bandwidth utilisation
- Identify attempts to access undesirable Internet resources
- Monitor usage of the Internet by site and/or by authenticated user
- Troubleshoot issues with packet filtering or rules
The Novell BorderManager HTTP Proxy maintains three types of log files:
- Common Log
- Extended Log
- Indexed Log
In general, the common log format provides sufficient information for analysis of outgoing proxy activity. In some circumstances, such as when using specialised log analysers, it may be appropriate to use the extended or indexed log formats.
This AppNote describes these logs, telling how each one can be enabled and configured and what information can be obtained from each of them. Also discussed is the use of WebTrends Firewall Suite, a popular analysis tool which can be used to report on the contents of the BorderManager Common Log file.
Check it out at http://developer.novell.com/research/appnotes/2002/january/02/a020102.htm
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com