WATCHGUARD HISTORICAL REPORTS EXPORT
Sawmill is a Watchguard Historical Reports Export log analyzer (it also supports the 1021 other log formats listed to the left).
It can process log files
in Watchguard Historical Reports Export format, and generate dynamic statistics from them,
analyzing and reporting events.
Sawmill can parse Watchguard Historical Reports Export logs, import them into a MySQL, Microsoft SQL Server, or Oracle database (or its own built-in database),
aggregate them, and generate dynamically filtered reports, all through a web interface.
Sawmill can perform Watchguard Historical Reports Export log analysis on any platform, including Windows, Linux, FreeBSD, OpenBSD, Mac OS, Solaris, other UNIX, and others.
Sawmill stores the following non-numerical fields in its database for Watchguard Historical Reports Export, generates reports for each field, and allows dynamic filtering on any combination of these fields:
| Field | | Internal Name |
|---|
| | date/time | | date_time |
| | day of week | | day_of_week |
| | hour of day | | hour_of_day |
| | type | | type |
| | direction | | direction |
| | firebox IP | | firebox_ip |
| | client IP | | client_ip |
| | protocol | | protocol |
| | message | | message |
| | bytes | | bytes |
Sawmill stores the following numerical fields in its database for Watchguard Historical Reports Export, aggregating them and including them as columns in most reports:
| Numerical Field | | Internal Name |
|---|
| | accesses | | accesses |
| | unique client IPs | | unique_client_ips |
| | bytes | | bytes |
See Sawmill Features to learn more about Sawmill's options for viewing, customizing, filtering, exporting and scheduling Watchguard Historical Reports Export reports.
Sawmill also supports 1021 other log formats.
