Oposite to the majority of webserver log analysis software, WebLogParser is based on a SQL database which stores the different the parts of the log lines. That way any kind of question about the data which can be phrased as an SQL statement can be answered.
To help you to get the most out of your logfiles WebLogParse offers this functionality:

  • Parsing the log
    • The standard parsing splits the log lines according to the Apache combined log file format.
    • If thats not enough, you may define a regular expression to split the line into the required database fields.
    • You may define regular expressions for private URLs like the administration interface of your CMS or your database administration tool. URLs matching one of those regular expressions are marked as private in the database and might be explicitly excluded from your query.
    • You may define regular expressions for helper files you're not really interested in when doing statistics. This includes graphic files, style sheets or javascript files. URLs matching one of those regular expressions are marked as helper files.
    • Extraction of search strings from the referrer by using regular expressions for known search engines. The search engines and the corresponding regular expressions are stored in the database. The major search engines are included but you can extend the table for your own needs.
    • Tag robot access to the pages. WebLogParse tries to identify robots during the logfile import by looking into the useragent and checking access to robots.txt. If you verify the collected useragents as robots, all future access with those useragents is marked in the database as access by a robot.
  • Queries against the log
    • WebLogParse comes with a set of predefined views and queries for useful information.
    • WebLogParse is extensible because it is based on a SQL database. Get any report which can be expressed as a SQL statement. Editing and execution of your own queries is supported.
    • For later reuse, store queries as view or query in the database.
    • Define queries with a parameter which can be filled from a column of the current results page.
  • Other features
    • Resolve IP addresses to hostnames or hostnames to IP addresses. Depending on the configuration of your webserver, you might have either hostnames or IP addresses in the remotehost field of the log. WebLogParse tries to resolve the missing information by doing a DNS lookup. The lookup is optionally because (although only done once per IP or hostname and import) it is very time consuming and slowing down the import considerably.
    • Send the content of columns of the result table to your default web browser if they start with http. Useful for looking at the results of the searches which routed users to your site.
    • Get geographical information about the visitor. With the optional Geo-IP database you get the country and if available the city where your visitor comes from. There are some drawbacks, however. For the details see here.