As you intend to test the query (the part of the URL that follows the “?”), you need to use URLWITHQUERY in place of URL in both the ExtraSectionCondition and the ExtraSectionFirstColumnValues.
I tried the URLWITHQUERY but this didn't work either. I also tried the URLWITHQUERY with the ”URL,^\\/forum\\/index.php\\?page=forumview" as there are plenty of log entries for this URL, but that didn't work either.
Do you have any suggestions on some test code that I can use to try and work out why it's not working?
It should work with URLWITHQUERY ! I tried your extra section here with a short log file that I created for the test and it was working fine.
Did you update the stats after you changed the extra section ? Changes will only be effective for the new log entries read by AWStats after you made the change in the extra section.
I updated the stats each time I changed the conf file. Also, a batch job updates the stats each night. I still have no entries for the extra section.
In the past I have ran the following command but this does not generate the right output either. I have a pretty standard install but I wonder if something is not working?
As you are using IIS, the visited URL's are split in two parts in the log file:
- cs-uri-stem (called %url by AWStats)
- cs-uri-query (called %query by AWStats)
For http://www.familylawwebguide.com.au/news/index.php?page=aries,
"cs-uri-stem" is "/news/index.php" and "cs-uri-query" is "page=aries".
As far as I can see, there is no cs-uri-query column in your log file. This should be changed in the IIS configuration if you need to monitor the query string.
The first line of your log file contains the list of fields present in the file.
I would suggest that you make a backup copy of the AWStats database file for July and August when your AWStats has completely processed that log file in the "old" format.
There are known problems in the implementation of LogFormat=2. AWStats should automatically take the change in format into account, but I I am not sure that this will happen.
On the other hand, if you use the extensive definition, you will need to split the log file into the part before the change and the part after the change in log format. The first part will have to be processed with the "old" LogFormat definition and the second part with the "new" one.
I have a number of EXTRA sections that I would like to run but this will make my default page very long. Is there a way to direct the output to a different page?
Upgrade to AWStats 6.9 and you will get a "Full list" option in the extra section. You can make the extra sections in the main report as short as you like and you get the full lists in separate reports.
By the way, this upgrade to 6.9 is recommended for security reasons too.
Sounds like the upgrade is worthwhile. Is there any documentation on the upgrade process?
I've had a quick look arround the awstats site, can't find anything. I guess I'll have to overwrite the existing files, update my conf file…anything else?
I noticed that 6.8 only came out last month, is it worth jumping to 6.9?
As a vulnerability was reported in 6.8 shortly after it was released, I recommend you upgrade to 6.9, not because of 6.9 features but for security reasons.
You upgrade by overwriting awstats.pl and the /lib, /plugins and /lang directories. As far as I know, there is no need to change an existing .conf file.
I've started to notice a difference in the pages column. The average appears to have dropped by about half from the previous month. Generally figures for this month are slightly lower. All other columns appear to be similar but the 'Pages' figure is significantly lower.
Average for July was 575 visitors with 13644 pages and 41451 hits
Average this month is 499 visitors with 6534 pages and 31496 hits
Has adding the 'cs-uri-query' influenced the figures?
I have deleted this months awstats file, split my log into two, and regenerated the awstats file with the two logs. When updating the secong log file (larger than the first), I got an error about an Extra section having too many extries. So both the logs were processed without any Extra sections in the conf file.
According to AWStats documentation, the file extension in cs-uri-stem determines what a page is. cs-uri-query should not have any influence.
If there are too many entries in some extra sections, change the ExtraTrackedRowsLimit directive in the config file (default is 500 rows) and/or consider to change the definition of the extra section in order to reduce the number of rows it produces.
I'm definitely getting some conflicting figures now and I'm not sure where to look for a solution or even what might be causing the descrepancies. You helped me out previously with creating an extra section to show what pages were displayed from particular directories, this section shows a total of 292348 (that is pages from all directories), whilst the summary section displays 144270.
How can I figure out the correct amount of pages?
Which figure is correct?
I ran an update for last months figures (the logs did not contain cs-uri-query) and the two figures are very similar (422974/427737).
The summary section shows the number of pages under "viewed traffic" and under "not viewed traffic". "Not viewed traffic" includes traffic from robots and HTTP errors. An extra section counts "viewed traffic" and robots traffic; HTTP errors are excluded.
So, total pages (all directories) from an extra section should be about the same as pages under "viewed traffic" plus pages under "not viewed traffic", if the number of HTTP errors is small (see section of the report titled "HTTP Status Codes").
Login 
Register 
Search 
Home
Print this Post 
Reply to Post
Add a New Topic
Quote and Reply 
Topic RSS 
