Firewalls and proxies generate a lot of log data. Multiple gigabytes per day are commonplace now. The log files themselves are generally simple flat text files. Their size comes from the sheer volume of entries, not from being rich data types. The log file size not only consumes disk space during logging, storing, and archiving, but [...]
Release Date: 3rd April 2013 Changes since 2.2.0.84: Log Formats: Apache: Alteration to Apache IBM format (duration field) Astaro: Fixed Date/Time field (time missing) ContentKeeper: Added support for new ContentKeeper syslog format IronPort: Added Ironport W3C format IronPort: Fixed Bounce Mail detection & importing IronPort: Renamed Ironport 'C350 mail' to 'C-series mail' IronPort: Improved C-Series [...]
We have released an automatic update for the Vantage range of applications. This update includes some new loader formats as well minor fixes and improvements. Of note, this release includes support for the new format of IronPort, Palo Alto Threat and URL filtering, Clearswift Email Appliance, and Infoblox NIOS DNS queries; as well as improvements [...]
In previous blogs I have covered why internet access is so important in the workplace, why blocking and filtering should be minimized, and why monitoring is preferred. Today I thought I’d focus on the specific benefits of monitoring and reporting on log files. To some it might be obvious, but plenty of search queries used [...]
Today I've been poking at Microsoft Exchange 2007 tracking logs, asking them the very simple question of 'How many emails have I sent?'. Unforunately, Exchange 2007 tracking logs are not used to simple questions, and are likely to return a complicated and / or misleading answer. But the confusion it seems, all comes down to definitions. Once you understand these definintions, things start to make a bit more sense.