polliwog polliwog is a Java-based Web-log processing tool/application that creates a website about your website visitors.
Download

polliwog Ranking & Summary

polliwog Tags

web Java web log log processing site logger polliwog

polliwog Description

polliwog is a Java-based Web-log processing tool/application that creates a website about your website visitors. polliwog is a Java-based Web-log processing tool/application that creates a website about your website visitors. Whilst most log processors focus on hits and pages, polliwog is more visit oriented.polliwog is more flexible than most processors. It provides an object model that represents the information in the log and so can harness the full power of Java and OO.polliwog project allows you to define the pages and sections produced in a XML-format so that end-users can customize the information displayed.It can convert the information in the log into a more "human-readable" form, no more strange URLs that make no sense.It tells you what a visitor looked at whilst browsing your site. It also provides a detailed breakdown of how visitors arrived at your site. In essence polliwog is a tool to help you understand how users interact with your site. See the features list for details of what polliwog can do.polliwog makes a very clear distinction between visits from search engines/spiders and human visitors. Log processing tools such as Webalizer do not and so lead to incorrect visitor figures. polliwog tells you which search engines have spidered your site and how many pages they have indexed.Here are some key features of "polliwog":· Number of human visitors (each visitor is classed as unique)· A page per visitor, displaying: start/end visit time, pages viewed, country of origin (provided by GeoIP lookup), User agent, visit time· For each page visited, the requested URI can be resolved into a human-readable name. The referer page is also displayed and again can be resolved into a human-readable name. If the visitor arrived from a search engine search this is resolved into a human-readable form as well. Also the size of the page requested is displayed as is the method, status code and date/time.· Visual summary (graph) of activity per-day, also a daily summary of activity.· Overall summary of activity for entire period.· Provides information about "site areas". As far as I can tell this is a concept unique to polliwog (but I may be wrong!). A "site area" is a logical grouping of pages within your site, it is defined by you and tend to be things like "shop", "help", "contacts". Site areas provide coarser information about how visitors interact with your site.· Visit paths, a logical usage of site areas is that of a visit path (again seems to be unique to polliwog). A visit path is basically the path that visitors took through your site by site area. For example they may have started at your "Front Page" area, then moved to your "products" area, then to your "support" area and then onto the "user" area. This gives you higher level information about the pathways through your site that users are taking and helps to identify areas where you may need to spend more time tailoring the pages in an area to keep visitors there.· Displays sites that link to yours.· Can produce compressed HTML files (need Web-server support to ensure that your browser can view them correctly).· Contains a webapp that allows for configuration and control of polliwog for any number of sites/logs.· User configurable pages and sections, you can decide which pages polliwog produces and the information it displays.· User configurable visit collections. This is basically the ability to define rules which will "collect" visits that match the rules (the default rules are defined by a JoSQL WHERE clause). You can then create pages that perform operations on those collections. This allows you to filter the visits into "buckets" that you can then get information on. For example, you may be interested in knowing which visitors have been to a certain page, or that have followed a certain "visit path" (for the pygmy possum site we have defined collections that tell us whether any visitors have purchased products that came from a MSN search, i.e. are our ratings on the MSN search engine actually leading to sales).· Information about each page is now generated. The search engine searches that led to the page being visited by a human being are shown, as are the number of times the page was hit, the number of unique human visitors and the number of times it was visited by search engine bots/spiders. Also the pages that "refer" to the page (referers) are shown along with their site areas, this provides details about how visitors are navigating to the page. Also, the external sites that link to the page are shown.What's New in This Release:New Features· JoSQLRule for hit/visit filtering· Added a new JoSQLRule that allows a External site, opens in new window JoSQL WHERE clause to be used to filter hits and visits.· Ability to collect filtered visits· See the visit filtering page for details.· Added a page resolver to determine what is a page· The page collector has been removed. A page resolver is now used instead to indicate what is a page.· Support for processing logs from a Java Application Server· polliwog can now process logs that are generated via the Java Application Server. See the log entry formats page for details.· Support for city lookups· Support has been added for performing city lookups of visitors via the External site, opens in new window MaxMind GeoIP city databases. Note: the city file is not provided with polliwog due to it's large size. See the GeoIP integration page for details on how to integrate GeoIP databases with polliwog.· New match type: JoSQLMatchType· A new match type, JoSQLMatchType, for use with Site Area resolution and Page Title resolution has been added. This match type allows a External site, opens in new window JoSQL WHERE clause to be used to resolve uri information into a site area/page title.· Support for property overrides· It is now possible to have your own properties file that overrides the standard properties that polliwog uses. This allows you to keep customized properties separate when upgrading polliwog to new versions. See the property overrides page for details.· Support for processing multiple log files· polliwog is now able to process multiple log files in succession via the use of a log file iterator. See the multiple log files page for details.· Better indication of why no visitors found in log· One of the main issues people have with polliwog occurs when no visitors are identified in the log. polliwog now provides an analysis of why this occurs and gives suggestions on how it can be rectified.· Better information when log processing has completed· When processing has completed, polliwog will output a summary of the information in the log file(s) and details of where it has written the files to.· Support for charts· polliwog now outputs pie charts for important information. Note: this feature makes use of the excellent External site, opens in new window JFreeChart.· Auto-detection of log format· polliwog will try and detect the format of hits in your log file(s). See the log entry formats page for details.· New property: queryParmsArePartOfPage added· Added new property: queryParmsArePartOfPage which when specified will mean that (if the page title cannot be resolved) then the query string will be considered as part of the page identifier. See the page title resolution page for details.· Support for image searches from search engines· Added support for resolving the results page/search engine and keywords used for image searches from search engines.· New navigation method· The navigation method has been changed to use a sidebar.· Search Engines have a family· The family for a search engine, i.e. where they get their results from has been added.· New pages detailing searches performed per search engine added· For each search engine identified by polliwog a page will be generated detailing all the searches performed by visitors that led to your site.Changes· Modified ExecPolliwogTask to use the system path separator to allow the classpath to be built up properly.· Deprecated DateRule and URLRule, a JoSQLRule should be used instead. See the hit filtering and visit filtering pages for details.· Updated External site, opens in new window JoSQL support to version 1.8.· Modified the SiteAreaResolver interface to take an instance of: AbstractURIField rather than a External site, opens in new window URI.· Remove timeZone support from DateTimeField, was not used and makes no difference in parsing.· Sets the JVM default timezone to the timezone specified by property timeZone. So don't use polliwog in a thread where other threads need to use the timezone (if it's different from your default).· Updated maxmind support to version 1.2.0.· Modified the BasicPageTitleResolver to be able to use a JoSQL match type to match a url against a page title.· Modified the PageTitleResolver interface to use an AbstractURIField rather than the path/parameters.· Moved page sets to use iterators rather than handler class types.· Updated GeoIP.dat file.· Modified the way that information about search engines is stored and organized. Now grouped by family.· Removed the SQL Execute Time from the linking-sites resuable section.· Property: logEntryFormat has been removed. See the log entry formats page for details.· Better identification of search bots/spiders (where they use different versions of the bot/spider).Bug Fixes· Made it so that the ip address of the visitor is actually displayed on the visit page.· Fixed problem with browser/os resolution when there is no user agent, will return unknown.

polliwog Related Software