totals

Simple example:
totals
#These are recommended
* Overall Accesses
/ Home Page Accesses
#An example: match documents belonging to a particular user
/~boutell*
end totals
Intermediate example:
totals
#Match all AOL users, rather than documents. Note the 'sites' keyword
sites *aol.com
end totals
Advanced example:
totals
/images/bobsad.gif Views of Bob's Ad
/cgi-bin/clickthrough.cgi/CT=http_3a_2f_2fwww_2ebobs_2ecom_2f Clickthroughs
function {Clickthroughs}/{Views of Bob's Ad}*100.0 Clickthrough Rate (%)
end totals
Note: in the web-based user interface, all of the totals entries are edited on a single page. when you add a "separator" using the Add Group Separator button, you are creating a new "totalsgroup--"aseparatebar graph.
The totals option, which extends for several lines and must end with the line end totals, is used to track various items over time. Frequently it is used to track the performance of certain documents or sets of documents. It is also possible to track the number of accesses from a particular ISP, the number of times users arrived at your site from a particular referring site, and more.

Typically each line of the totals option contains a pattern and a title for that pattern. Wusage will count the total number of accesses to and bytes served of that pattern, and in the case of daily, weekly and monthly reports, a bar graph of that pattern's popularity over time will be generated. A separate bar chart is generated for each item. To compare several items on the same bar chart, see the totalsgroup option.

The two patterns shown in the simple example above match all documents and the home page document, respectively. Each character of each document name is matched against each pattern in the totals list. An * in a pattern matches any number of characters in a document name. Patterns have additional features; for more information, see the patterns section. If the totals ... end totals option is not specified, no totals will be generated.

The totals option may appear as many times as desired, usually in alternation with totalsgroup options, but the same pattern should not appear more than once.

Tracking More Than Just Documents

In addition to document accesses, the following additional types of information can be measured using the totals option. Patterns which track sites, referring URLs, and so on look just like patterns used to track documents, except for the identifying keyword which appears first on the line. Note that separate reports are also available that provide more information about each of these topics. For your convenience, links to the appropriate sections of the documentation are provided in the table below.
To Measure...Use This KeywordSee Also...
DocumentsdocumentsDocuments Report
Missing FilesnotfoundNot Found Report
Accessing SitessitesSites Report
Sites Accessed via Proxy ServerproxysitesProxy Sites Report
User Agents (Web Browsers)useragentsUser Agents Report
Referring URLsreferrersReferring URLs Report
Referring SitesreferringsitesReferring Sites Report
Authorized UsersauthusersAuthorized Users Report
DomainsdomainsDomains Report
Domains Accessed via Proxy ServerproxydomainsProxy Domains Report
VisitsvisitsVisits Report
TrailstrailsTrails Report

Tracking Unique Sites (or Documents, or...)

Often it is desirable to know how many unique sites visited your server. That is, if the server is accessed a thousand times, this does not mean that 1,000 different people accessed the server. To track the number of unique items, use the special keyword unique instead of a normal pattern.

New in Wusage 6.0 P19: Trail and Visit Patterns

As of version 6.0 P19, it is now possible to match visits that included particular document. This results in a count of the number of visits that crossed that document. It is also possible to match trails that mention a particular document, in which case the number of unique paths crossing that document is measured. For example:
visits http://*yahoo.com*/product/download.html* Yahoo -> Product Download Page
This entry counts the number of visits that began on Yahoo and passed through a particular page. Note that "outside" URLs like this can be included only if referring URLs are present in your log files.

Functions

The advanced example shown above includes a special function line. Instead of matching a certain document, this line's value is computed by performing arithmetic on the other entries. Functions can use the + (addition), - (subtraction and negation), * (multiplication), and / (division) operators. Numbers can appear, with or without a decimal point. Calculations are carried out according to the normal rules of algebra. Parentheses are also allowed. Most importantly, references to the results of of earlier lines are allowed, much like references to another cell in a spreadsheet program. Functions can make a reference to any prior entry in a totals or totalsgroup option. In the above example, {Clickthroughs} refers to the result of the previous line which matched all outgoing clicks going to a particular advertiser's site. The clicks are counted through the use of the provided clickthrough.cgi CGI program.

NOTE THAT THERE SHOULD BE NO SPACES IN A FUNCTION, EXCEPT BETWEEN { AND }. Otherwise the function will be confused with its label.

When You Don't Want A Graph

If you do not want a particular line's result to be graphed, put the special keyword nograph in front of the line:
nograph /cgi-bin/bob Accesses to Bob
This line's value will still be calculated, and it will appear in the table of results, but it will not be graphed.

When You Don't Want A Total (in the Table of Results)

If you do not want the values over time for a particular line to be summed for a grand total in the table of numeric results, which normally shows the average, total and latest values for each line, put the special keyword nototal in front of the line:
nototal /cgi-bin/bob Accesses to Bob
This is useful when it would be meaningless to add up the values from different days, weeks or months. (For instance, it does not make sense to add up each week's clickthrough percentages for a "grand total.")

Putting It All Together

Note that you can use nograph, nototal and function together, if you wish to do so. This is useful when you wish to compute something in several steps and refer to the results of each step in another function later in the configuration file.
Wusage Home Page Configuration File Reference Index

Copyright 1998, 1999, Boutell.Com, Inc.
Contact Us


Boutell.Com, Inc - PO Box 63767, Philadelphia PA, 19147, USA
Phone/Fax +1 206. 658. 8176


Follow us on Twitter | Contact Us

Copyright 1994-2012 Boutell.Com, Inc. All Rights Reserved.