Web Reporter has default data points for reporting. If you want additional info, there are four custom columns available for reporting on additional data. However, these additional columns have some restrictions.
Only available in detail data / not available in summary data
Only for advanced reports (requiring a premium license)
No special data type recognition. For example, byte values will not calculate sum or average values, IP addresses cannot be filtered by a netmask, etc.
There are 3 primary steps for getting Web Reporter to report on additional info.
Configure the Web Gateway to include the desired field in the access log.
Update the Web Gateway’s access log header to reflect the change made in step one.
On Web Reporter, modify your log source by adding a User-Defined Column for this new log header, so WR can understand this particular access.log format.
Example using destination IP
We often see that administrators want to run reports based on, or to at least include the destination IP, so we will use destination IP as an example for adding a custom column.
**Before going any further, it is important to know that if there is any misconfiguration on the Web Gateway side, then none of your access logs will be processed by Web Reporter until this is corrected. Any affected logs may not be able to be repaired. Therefore, we recommend testing the changes on a practice access log first. Instructions for creating a practice log can be found here, under the “Creating a Customized log” section:
Following the advice below about headers will prevent much frustration, as ANY type of error with headers will prevent Web Reporter from understanding the log format, and it will not process any corresponding logs.
Other than underscore (_), no other special characters are permitted
Header names cannot contain spaces. Use an underscore wherever a space is desired (server_ip)
If the field logged was wrapped in double quotes, then wrap the header name in double quotes as well
Avoid duplicate names – do not give it name that already exists in the Log header
As a general rule of thumb, the example below is always a safe approach to header names: "mwr_header_name"
On Web Reporter, modify the log source by adding a User-Defined Column for the new log header
Now that the Web Gateway is logging the destination IP and the access log header has been updated, you must modify your log source inside of Web Reporter. Note that, if you have multiple Web Gateway log sources in Web Reporter, you have to make sure to update all of them.
Add a User-Defined Column for this new log header (server_ip) so that WR can use this particular access.log format and so that you can report using it. To modify the header, you can take the following steps:
Log into your Web Reporter
Navigate to Administration -> Setup ->Log Sources -> Log Sources.
Select your log source, and hit ‘Edit’.
On the ‘Edit Log Source’ screen, click the‘User-Defined Columns’ tab.
Assuming you aren’t already using it, check the checkbox for User-Defined 1 to ‘Populate this column’, and enter a Log file header of server_ip (assuming of course, you used server_ip as your header on the MWG side).
Now, any further log files coming into Web Reporter from this log source should have this new log entry parsed and added to the User-Defined 1 column. You can use this when running advanced reports on detail data. It’s important to note that all data prior to when this change was made will not have this data available to report on.