| User | Post |
|
7:42 am
November 12, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
Hi, I would like to display the average latency per URL, and I was hoping this could be achieved via an ExtraSection, but I cannot see how this is possible if I can only create one user defined column. Am I missing something? Or should I be looking at doing this another way? Is it possible to extend or customise the report letters (i.e. PHB) to include latency? Thanks.
|
|
|
8:06 am
November 12, 2008
|
Jean-Luc
| | |
| Admin
| posts 1042 | |
|
|
Hi,
You cannot add another user-defined column in an extra section. There is no nice way to do what you are looking for.
Here is a possible workaround. Create a second AWStats config file and use the %bytesd field for the latency. The “Pages-URL (Top 10) ” in the generated reports will show the average latency in the “Average size” column.
|
|
|
10:39 am
November 12, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
Hi
Not sure I understand your use of %bytesd to represent latency, since latency is measured in milli-seconds. Besides I already have latency as the last value in a log file entry. Also, I do not know how to use %bytesd for latency in the AWStats config file, since the only use I can see for this parameter is in the LogFormat. Can you please explain further. Many Thanks.
|
|
|
10:50 am
November 12, 2008
|
Jean-Luc
| | |
| Admin
| posts 1042 | |
|
|
I understand that my suggestion sounds strange. ;-)
I suggested that you create a second conifg file that will use %bytesd in an unusual way. In the second config file, %bytesd will be used as latency field. By doing that, you will not get any valid “bandwidth” or “average size” in the report, but you will get the “average latency” in the place in the “Pages-URL (Top 10)” section. I hope this is more clear.
I did not try it myself, but I believe it should work if “latency” is an integer number.
|
|
|
11:09 am
November 12, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
So do you mean replace ShowPageStats=PBEX with P%bytesdEX?
|
|
|
11:21 am
November 12, 2008
|
Jean-Luc
| | |
| Admin
| posts 1042 | |
|
|
No, I don't mean that. %bytesd must be placed in the last field of your LogFormat definition as you wrote that latency is the last value in a log file entry. Do not change anything else and re-run the update.
|
|
|
12:00 pm
November 12, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
OK, I changed LogFormat to "%cluster %host %other %logname %time1 %methodurl %code %bytesd %uaquot %bytesd", and updated the AWStats db. But the Pages-URL report still contains KB and Bytes in the Average size column. Not sure if the actual values are any different though.
|
|
|
12:15 pm
November 12, 2008
|
Jean-Luc
| | |
| Admin
| posts 1042 | |
|
|
I am puzzled by your post…
You wrote: "Not sure if the actual values are any different though. " It should not be complicated to compare the figures in the regular AWStats report with the figures in the new report.
For information, I can also configure this for you for a very small fee. Send me a private message if you are interested.
|
|
|
12:46 pm
November 12, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
I changed LogFormat back to “%cluster %host %other %logname %time1 %methodurl %code %bytesd %uaquot %extra1”, and saved a copy of the db file to awstats112008.txt.bck02. Then I updated the AWStats db, and this is the difference between the backed up file (using %bytesd) and newly created version (using %extra1):
-rw-r–r– 1 cl sys 149676 Nov 12 19:46 awstats112008.txt.bck02
-rw-r–r– 1 cl sys 149676 Nov 12 20:22 awstats112008.txt
-> diff awstats112008.txt awstats112008.txt.bck02
51c51
< LastUpdate 20081112202201 0 0 0 0 0
—
> LastUpdate 20081112194632 0 0 0 0 0
668a669
> 10.225.130.5 254 580 4518799 20081112181010
671d671
< 10.225.130.5 254 580 4518799 20081112181010
So not a lot of difference there.
BTW, the Average size values are the same in both reports. What I was expecting was since the previous report used %bytesd that it would omit the KB and Bytes notation.
|
|
|
1:43 pm
November 12, 2008
|
Jean-Luc
| | |
| Admin
| posts 1042 | |
|
|
The units in the report will still be Bytes or KBytes : Bytes = milliiseconds and KBytes = seconds. As I said in my first post above, there exists no nice way to do it.
There is no difference between your two files, except the update timestamp. At least one of the updates did not work properly.
When testing with AWStats, it is (highly) recommended to start from an empty AWStats database. You can temporarily move the existing database files to another directory. It is also recommended to run the update from the command line and to record the messages coming from awstats.pl.
It is hard to say exactly what happened from here, but it could be that no update was done because AWStats considered that no new data was available.
|
|
|
4:30 pm
November 14, 2008
|
flash
| | |
| Member | posts 6 | |
|
|
Thanks Jean-Luc. You were correct in that no update was done by AWStats, because there was no new data. I used the workaround you suggested and the report now displays latency. Many Thanks.
|
|
Login 
Register 
Search 
Home
Print this Post 
Reply to Post
Add a New Topic
Quote and Reply 
Topic RSS 
